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

[Feature request] Add ability to configure stacks (tracking branch) #211

Closed
jandroav opened this issue Jan 9, 2024 · 2 comments
Closed
Labels
feature A new feature request

Comments

@jandroav
Copy link

jandroav commented Jan 9, 2024

I would like to have a spacectl stack configure --id STACK_ID --branch staging command.

There can be ci/cd workflows where it is needed to deploy resources from a branch different than the stack configured one.

spacectl stack deploy always deploys what is pushed to the tracking branch. I can not deploy resources from another branch without manually changing the stack tracking branch. Imagine the following workflow:

  1. PR opened from a feature branch to main
  2. A GitHub action runs a spacectl stack local-preview. If everything is ok it deploys resources to a staging AWS account
  3. PR merged to main
  4. A GitHub action runs spacectl stack deploy so resources are deployed to a prod AWS account

Step 2 is not currently possible because spacectl stack deploy can not deploy stuff from the current feature branch.

I see 2 options:

  1. A new subcommand like: spacectl stack configure --id STACK_ID --branch staging
  2. A new option like: spacectl stack deploy --id STACK_ID --branch

I hope it all makes sense.

@tomasmik tomasmik added the feature A new feature request label Jan 9, 2024
@tomasmik
Copy link
Contributor

tomasmik commented Aug 29, 2024

We will not be adding any features which alter data inside of your spacelift account.

@jandroav
Copy link
Author

Option 2 does not change data inside the Spacelift account @tomasmik

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

No branches or pull requests

2 participants