Fix nil pointer error in registry sync when merging fails with an unknown error #744
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.
What changed?
Return an error when merging fails with any error other than awsmerge.DuplicateProfileError
Why?
In some cases when merging profiles fails with an error other than awsmerge.DuplicateProfileError the error was not logged and the code would continue, expecting the configFile to be non nil.
This would cause a nil pointer error
How did you test it?
Locally
Potential risks
Low, the registry sync is a non blocking task, it will now correctly log an error instead of panicing
Is patch release candidate?
yes
Link to relevant docs PRs