fix: normalize values file naming to dash convention - #5
Open
shikanime wants to merge 2 commits into
Open
Conversation
Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: I77aaadb86db2a1703921f70db8a63d2c6a6a6964
Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: If6d0fcc2482e9ddeb9125d6c1d5832366a6a6964
shikanime
marked this pull request as ready for review
August 26, 2026 13:04
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
1 participant
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.
Issues liées
#3 (fermer délibérément après la fusion)
Quel est le comportement actuel ?
Deux conventions de nommage coexistent :
values-<env>.yaml(tiret) etvalues.<env>.yaml(point).Quel est le nouveau comportement ?
Tous les overlays suivent la convention tiret :
values.cpin-hp.yamldevientvalues-demo-cpin-hp.yaml(nom distinct, il pointe vers le projetdemo/*),values.formation-dev.yaml,values.formation-zone.yaml,values.minarm.yamletvalues.prod.yamlsont renommés en conséquence.Cette PR introduit-elle un breaking change ?
Non pour le chart ; les pipelines externes qui référencent ces noms de fichiers devront suivre les nouveaux noms.
Autres informations