Investigate patches for recent Gatekeeper normalizations #99
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.
DO NOT MERGE
Only opening a PR here for potential discussion.
This is more of a quick experiment in order to figure out what would be
needed to get specs passing that are equivalent to the current
Gatekeeper specs.
I have marked all specs as pending that:
There is only one remaining case that I think we should continue
supporting:
travis-yaml only accepts env vars given as a Sequence:
While Gatekeeper also accepts them when given as a Map:
The same goes for nested global and matrix keys:
versus: