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

Support for passing existing environments in project spec file for update command #187

Closed
abhijeetkaurav1st opened this issue Aug 23, 2021 · 2 comments · Fixed by #202
Closed
Labels
P1 Critical

Comments

@abhijeetkaurav1st
Copy link
Collaborator

calm update project -f <project_file>. command update the project with the file data. All data is overrided as of now.
Need a way to pass existing environments in project file.
Ex:

class Project1(Project):
     envs = [Env1, Env2]
     env_refs = [Ref.Environment("Existing environment with this project")]

Where env_refs will take existing environments to be remain in the project

@abhijeetkaurav1st abhijeetkaurav1st added the P1 Critical label Aug 23, 2021
@abhijeetkaurav1st
Copy link
Collaborator Author

Or much better, if during update we will not remove existing envs from project also.

@glover-chris
Copy link

glover-chris commented Nov 8, 2021

Agree with your above better comment. We use separate environment files and do not create envs within the project file. Maybe a switch at project update which will not remove existing? Also a switch to ensure users/groups are not removed from the project if not included in the project.py file (most customers want to separate their envs and users/groups from the project file in order to keep them as atomic as possible.

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

Successfully merging a pull request may close this issue.

2 participants