You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.
├── aggregate // has guestbook-a and guestbook-b as bases
│ └── kustomization.yaml
├── guestbook-a // has template as a base, renamed using json6902
│ ├── kustomization.yaml
│ └── rename.yaml
├── guestbook-b // has template as a base, renamed using json6902
│ ├── kustomization.yaml
│ └── rename.yaml
└── template // single resource
├── guestbook.yaml
└── kustomization.yaml
When trying to build the aggregate directory (which simply includes guestbook-a and guestbook-b as bases), it fails with:
$ kustomize build aggregate
Error: ../guestbook-b: id '"~G_v1_Pod|~X|~P|guestbook|~S"' already used
aggregate/kustomization.yaml
bases:
- ../guestbook-a
- ../guestbook-b
Both of the guestbook-a and guestbook-b directories rename the same resource in the template base using json6902:
The text was updated successfully, but these errors were encountered:
jessesuen
changed the title
Unable to include two bases that have same parent: id already used
Error: id already used when includi two bases that rename same resource in parent
May 17, 2019
jessesuen
changed the title
Error: id already used when includi two bases that rename same resource in parent
Error: id already used when including two bases that rename same resource in parent
May 17, 2019
I have the following kustomize structure:
When trying to build the aggregate directory (which simply includes guestbook-a and guestbook-b as bases), it fails with:
$ kustomize build aggregate Error: ../guestbook-b: id '"~G_v1_Pod|~X|~P|guestbook|~S"' already used
Both of the guestbook-a and guestbook-b directories rename the same resource in the template base using json6902:
The failing example can be reproduced here:
https://github.com/jessesuen/k8s-deployments/tree/master/kustomize-json6902-rename-already-used
The text was updated successfully, but these errors were encountered: