You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Be able to create an environment without directly deploying to it, to be able to set environment variables for the environment
Cancel a deployment by its identifier
Describe alternatives you've considered
Start the new environment with a deployment and directly cancel the deployment
Set the environment specific variables as environment variables at project level and remove after the environment has been created
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
The text was updated successfully, but these errors were encountered:
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
Describe alternatives you've considered
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 RepositoryAdditional context
N/A
The text was updated successfully, but these errors were encountered: