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

qbec env add / qbec env del #47

Open
kvaps opened this issue Jul 21, 2019 · 5 comments
Open

qbec env add / qbec env del #47

kvaps opened this issue Jul 21, 2019 · 5 comments

Comments

@kvaps
Copy link
Contributor

kvaps commented Jul 21, 2019

Need automation for adding and removing environments, with describing them in environments directory and params.libsonnet, qbec.yaml files

@gotwarlost
Copy link
Contributor

since qbec doesn't have an opinion on how to create runtime parameters and where environment specific configuration is stored, it cannot reasonably update these. The best it can do is add an environment entry in qbec.yaml. The rest of the structure can be vastly different for every project.

@kvaps
Copy link
Contributor Author

kvaps commented Jul 29, 2019

But it is doing that for the initial default environment. Isn't it?

@gotwarlost
Copy link
Contributor

Yes and I want to change that. The generated code is too much machinery to get started. I want qbec init to produce something like the config documented at https://qbec.io/userguide/usage/runtime-params/#using-qbec-io-env

@kvaps
Copy link
Contributor Author

kvaps commented Jul 30, 2019

Please keep it simple for end user.

Allowing users to cusomize main structure is cool idea, but current example is really fine for the beginners who have no much experience with jsonnet.

Separate environments same way as components are a good starting point to start this familiarity.

@kvaps
Copy link
Contributor Author

kvaps commented Jul 30, 2019

Maybe leave this hierarchy structure only for init --with-example?
I think it is good compromise to solve that, and keep simplicity for beginners :)

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

No branches or pull requests

2 participants