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

fix: use LAGOON_ENVIRONMENT_VARIABLES as primary source #410

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

rocketeerbkw
Copy link
Member

In uselagoon/lagoon#3856, Lagoon core will consolidate env vars before sending to Lagoon remote, so LAGOON_PROJECT_VARIABLES may be empty.

Eventually LAGOON_PROJECT_VARIABLES will be empty
Copy link
Member

@shreddedbacon shreddedbacon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine to me. Incorporating the backwards compatible project variable check on the necessary variables solves the main concern.

As this is compatible with the current version of lagoon with uselagoon/lagoon#3856 not yet merged (at the time of review) this is fine to be merged without the other being merged.

@shreddedbacon shreddedbacon added this to the 2.24.0 milestone Feb 11, 2025
@shreddedbacon shreddedbacon merged commit be3dadf into main Feb 11, 2025
2 checks passed
@shreddedbacon shreddedbacon deleted the org-env-vars branch February 11, 2025 22:32
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

Successfully merging this pull request may close these issues.

2 participants