Skip to content
New issue

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

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

Already on GitHub? # to your account

fix: only init/select stacks in relevant project directories #114

Closed
qdzlug opened this issue Mar 15, 2022 · 0 comments · Fixed by #167
Closed

fix: only init/select stacks in relevant project directories #114

qdzlug opened this issue Mar 15, 2022 · 0 comments · Fixed by #167
Labels
enhancement New feature or request

Comments

@qdzlug
Copy link
Contributor

qdzlug commented Mar 15, 2022

Describe the bug
Once upon a time when the project was new we only had project directories that corresponded with what we were deploying. As we've added in more choices of infrastructure as well as utility and supporting projects we are in a position where we have projects that are only used in certain configurations. Yet, we still create the stack in the project directory, which is one more thing to clean up post run.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy the application.
  2. Check a non-used project (ie, so the AWS directories if this is a DO or LKE deployment).
  3. There will be a stack created in the non-used project.

Expected behavior
We should only create stacks in the projects we are going to use.

Your environment

  • n/a

Additional context
n/a

@qdzlug qdzlug added the enhancement New feature or request label Mar 15, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant