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

Cancel deployment from CLI #411

Open
sjerdo opened this issue Dec 12, 2024 · 0 comments
Open

Cancel deployment from CLI #411

sjerdo opened this issue Dec 12, 2024 · 0 comments

Comments

@sjerdo
Copy link

sjerdo commented Dec 12, 2024

Is your feature request related to a problem? Please describe.

For some of our projects, we need to set some environment variables at environment level before the first deployment. Creating an environment without starting a deployment currently is not possible.

If we are able to cancel a deployment, we could start a deployment and directly cancel the deployment to create an environment in lagoon without actually deploying it. This allows us to set the correct environment variables (via CI / CLI) and then start a new correct deployment

Describe the solution you'd like

  1. Be able to create an environment without directly deploying to it, to be able to set environment variables for the environment
  2. Cancel a deployment by its identifier

Describe alternatives you've considered

  1. Start the new environment with a deployment and directly cancel the deployment
  2. Set the environment specific variables as environment variables at project level and remove after the environment has been created
  3. Start a build using lagoon deploy branch --project {PROJECT} --branch {ENVIRONMENT_NAME} --branch-ref NONEXISTENTHASH if the environment does not exist, so the first build will fail at stage Checkout Repository

Additional context
N/A

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

1 participant