Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow selection of target cloud using environment variables #592

Open
sudeephb opened this issue Feb 16, 2023 · 1 comment
Open

Allow selection of target cloud using environment variables #592

sudeephb opened this issue Feb 16, 2023 · 1 comment

Comments

@sudeephb
Copy link

sudeephb commented Feb 16, 2023

If there are two or more clouds associated to a single controller, zaza chooses one of the clouds by itself to deploy the test models. It is possible to specify a particular cloud using the zaza config file. It would be convenient to be able to set an environment variable like ZAZA_CLOUD_NAME to specify the cloud where the models for testing will be deployed.

@ajkavanagh
Copy link
Collaborator

I think this opens up an interesting question of reviewing how zaza gets its configuration. It would probably be nice to be able to specify config via:

  • command line arguments.]
  • the zaza config file
  • via environment variables prefixed with ZAZA_

If a common set of variable names existed across all three mechanisms, then it would become much easier to understand how to configure zaza before a test run.

Back to this request: yes, I see this as a useful addition, where the env variable would override the config file (if it existed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants