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(yaml) specifying a value takes precedence over the source input #363

Merged
merged 1 commit into from
Nov 12, 2021

Conversation

dduportal
Copy link
Contributor

Fix #359 .

Depends on #360 and #362

Test

To test this pull request, you can run the following commands:

go build -o ./dist/updatecli && ./dist/updatecli diff --config ./examples/updateCli.generic/yaml.yaml

Additionnal Information

  • Added unit tests for yaml target (not complete coverage: Yaml encoder mocking ain't easy)
  • Factorized code in yaml target to ensure the same behavior between SCM and non SCM
  • Ensure that logging is reusing the constants for the unicode emojis

@dduportal dduportal added bug Something isn't working resource-yaml Resource of kind YAML target Related to updatecli target labels Nov 11, 2021
Signed-off-by: Damien Duportal <damien.duportal@gmail.com>
Copy link
Member

@olblak olblak left a comment

Choose a reason for hiding this comment

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

:shipit: :

@olblak olblak merged commit 78cba63 into updatecli:main Nov 12, 2021
@dduportal dduportal added this to the 0.14.1 milestone Nov 13, 2021
@dduportal dduportal deleted the gh-359 branch November 17, 2021 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resource-yaml Resource of kind YAML target Related to updatecli target
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[yaml] attribute 'value' is ignored by targets
2 participants