-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Error during expansion of "!!merge <<:" anchor tags #4212
Comments
Second issue is indeed #3446. |
/retitle Error during expansion of "!!merge <<:" anchor tags |
Thanks @eddiezane @KnVerey, the integer key is the second issue, confirmed that it works fine when I put it in quotes. |
/triage accepted |
I am currently still receiving errors on the below yaml snippet (from https://github.com/knative/eventing/releases/download/v0.26.0/eventing-core.yaml) :
The error received is:
Please advise - thanks! |
I'm having this same issue, I tried to understand more deeply the issue and come up with a solution... I'm still reading the Contribution Guidelines, and I was not sure if I could do it because I'm not familiar with the codebase. I opened a PR on my fork, and I'm still dealing with some corner cases related to comments and JSON serialization... After signing the CLA I can open this PR if there's nothing terribly wrong with it 😅 |
@RafaeLeal I took a very quick glance at your PR, and nothing about it seems terribly outlandish, it would be great if you could open the PR here and we can do a more thorough review. |
@natasha41575 Created, thanks! :) |
Closed by #4383 |
This is a follow up issue to #3675 as we still see errors when using the kustomize version 4.4 that has the YAML anchor fix. We're also seeing a similar error (
unsupported type: map[interface {}]interface {}
) for some other YAML in knative that doesn't have a YAML anchor.We use kustomize v3.8.10 which works fine with knative but we get errors when using the later versions that use kyaml.
kustomization.yaml
The YAML anchor in serving-domainmapping.yaml and serving-core.yaml looks like this:
Error during build:
The non YAML anchor related error example is in release.yaml:
The error we get is here:
The text was updated successfully, but these errors were encountered: