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

feat: allow lenient yaml unmarshal #2899

Closed

Conversation

nitrocode
Copy link
Member

what

  • feat: allow lenient yaml unmarshal

why

  • Allow top level keys for yaml anchors outside of the projects key

tests

  • I have tested my changes by running make test

references

@nitrocode nitrocode added the needs discussion Large change that needs review from community/maintainers label Dec 29, 2022
@nitrocode nitrocode requested a review from a team as a code owner December 29, 2022 22:52
@GenPage
Copy link
Member

GenPage commented Jan 4, 2023

Have we fully considered the implications of switching from strict unmarshalling? Are there any edge cases we haven't considered in regards to how we validate the config?

From what I understand reading the yaml lib docs, it will just silently ignore any key added to the YAML file that does not have a corresponding field in the config struct

@nitrocode
Copy link
Member Author

Yes exactly.

From the maintainers meeting, this would only be allowed to merge if this was gated behind a flag. It's not super critical to me. If someone would like to pick this back up and put it behind a flag, please feel free. I will close this for now

@nitrocode nitrocode closed this Jan 25, 2023
@nitrocode nitrocode deleted the allow-lenient-yaml-unmarshal branch January 26, 2023 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs discussion Large change that needs review from community/maintainers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Relax atlantis.yaml validation
2 participants