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

Operator assumes stack creation if it doesn't exist #185

Closed
elsesiy opened this issue Aug 25, 2021 · 0 comments · Fixed by #186
Closed

Operator assumes stack creation if it doesn't exist #185

elsesiy opened this issue Aug 25, 2021 · 0 comments · Fixed by #186
Assignees
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@elsesiy
Copy link
Contributor

elsesiy commented Aug 25, 2021

The current implementation always assumes that a stack that doesn't exist in the tracking git repo to be automatically created, see here.

This could be problematic as users might want to decouple the stack creation from the stack CR creation (often live in different repos). Stacks often require certain configs to be present and assume the default values as part of the created stack by the stack CR might not be desirable.

@elsesiy elsesiy added the kind/enhancement Improvements or new features label Aug 25, 2021
viveklak pushed a commit that referenced this issue Aug 30, 2021
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Aug 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants