vmware
Here are 733 public repositories matching this topic...
-
Updated
Nov 15, 2021 - Shell
-
Updated
Oct 1, 2021 - PowerShell
I'm in the app folder.
I mkdir exports to make an export folder.
I run rake evm:export:service_dialogs -- --directory exports
I get back:
(in /var/www/miq/vmdb)
Error: argument --directory Destination directory must exist.
Try --help for help.
How can this be? I can ls and see my exports folder in this directory.
-
Updated
Jan 6, 2021 - Shell
-
Updated
Oct 19, 2021 - PowerShell
-
Updated
Nov 15, 2021 - Shell
-
Updated
Nov 15, 2021 - C++
-
Updated
Oct 22, 2021 - Go
-
Updated
Sep 13, 2020 - Shell
-
Updated
Nov 10, 2021 - Shell
-
Updated
Nov 15, 2021 - PowerShell
-
Updated
Sep 23, 2021 - Ruby
-
Updated
Aug 30, 2019 - Shell
-
Updated
Nov 15, 2021
We need a better test of the helm chart and log-router. We should load the helm chart but we also need to wait until log-router and reloader start up with a very minimal config. This is just to make sure the helm values.yaml can be passed to the config-reloader without making it crash.
This will catch bugs such as this one recently: vmware/kube-fluentd-operator#205
Ro
-
Updated
Feb 3, 2020 - PHP
-
Updated
Oct 1, 2021 - PowerShell
-
Updated
Jun 18, 2021 - Roff
-
Updated
Aug 1, 2021 - C++
-
Updated
Nov 15, 2021 - Python
-
Updated
Feb 7, 2019 - C
-
Updated
Oct 19, 2021 - RobotFramework
Improve this page
Add a description, image, and links to the vmware topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vmware topic, visit your repo's landing page and select "manage topics."


What would you like to be added:
Our presubmits prowjobs have a linter which validates a lot of variables on the job definition like service account, make target, etc. It would be good value add, if we can validate the env vars as well.
Why is this needed:
This prevents from checking in, undesirable env variables that would not work for the prow job. An example would be a wrong bucket