Push the .lagoon.yml file into a configmap #2375
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shreddedbacon
force-pushed
the
configmap-lagoonyml
branch
from
fb422ce to
07b4fed
Compare
Schnitzel
approved these changes
Dec 13, 2020
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
At the end of a deployment, the .lagoon.yml will get put into a configmap named
lagoon-yaml.This is handy to have for troubleshooting when builds may not put the .lagoon.yml into a running image.
I put it at the end of a deployment, but I'm not sure if this is the best place for it?
Closing issues
Put
closes #XXXXin your comment to auto-close the issue that your PR fixes (if such).