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

add LAGOON_NEW_DEPLOYMENT or similar variable on first build #155

Open
tobybellwood opened this issue Jul 25, 2022 · 1 comment
Open

add LAGOON_NEW_DEPLOYMENT or similar variable on first build #155

tobybellwood opened this issue Jul 25, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@tobybellwood
Copy link
Member

tobybellwood commented Jul 25, 2022

It would be handy to be able to utilise a variable in the build that could determine if it's the first deployment into a namespace.

This can then be used in pre/post rollout tasks without having to workaround

This could possibly be implemented in the remote-controller

@shreddedbacon shreddedbacon transferred this issue from uselagoon/build-deploy-tool Aug 1, 2022
@shreddedbacon
Copy link
Member

Moved to remote-controller as this is where this logic will need to live. Basically when the namespace is created, we can inject this variable into the build pod.

For naming:

  • LAGOON_NEW_DEPLOYMENT
  • LAGOON_FIRST_DEPLOYMENT
  • ?

@shreddedbacon shreddedbacon added the enhancement New feature or request label Aug 1, 2022
@shreddedbacon shreddedbacon self-assigned this Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants