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

chore(manifest): upgrade UnmarshalYAML to v3 and add for Image #2861

Merged
merged 2 commits into from
Sep 22, 2021

Conversation

iamhopaul123
Copy link
Contributor

@iamhopaul123 iamhopaul123 commented Sep 22, 2021

This PR

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the Apache 2.0 License.

@iamhopaul123 iamhopaul123 requested a review from a team as a code owner September 22, 2021 03:46
@iamhopaul123 iamhopaul123 requested review from efekarakus and removed request for a team September 22, 2021 03:46
@mergify mergify bot merged commit 1a6f7ff into aws:mainline Sep 22, 2021
thrau pushed a commit to localstack/copilot-cli-local that referenced this pull request Dec 9, 2022
)

<!-- Provide summary of changes -->
This PR
- upgrade `UnmarshalYAML` to yaml v3 because of go-yaml/yaml#125 (comment)
- add `UnmarshalYAML` for `Image` to validate mutual exclusive fields before applying env override.
- Revert `Image` struct [embedding](https://golang.org/doc/effective_go#embedding) in `ImageWithHealthcheck` and `ImageWithPort`, as `UnmarshalYAML` would be wrongly taken as the method of its parent, causing the other fields in its parent struct (e.g., `Port` and `HealthCheck`) to be set `nil` unexpectedly. go-yaml/yaml#263 (comment)
<!-- Issue number, if available. E.g. "Fixes aws#31", "Addresses aws#42, 77" -->

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the Apache 2.0 License.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants