Closed
Conversation
9a933e4 to
9e1a4af
Compare
9e1a4af to
5818c0c
Compare
Member
|
@kimminw00, did you intend to close this? |
Contributor
Author
I found a problem with my code. |
This file contains hidden or 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
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.
I would like to propose allowing template values to git-sync repo url.
Why is it needed?
Let's assume that we're providing airflow service to multiple teams.
By creating git-sync repo urls using
{{ .Release.Namespace }}or{{ .Release.Name }},there is no need to create multiple values files to store different hostnames for each team.
Usage