-
Notifications
You must be signed in to change notification settings - Fork 241
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
🏃 Change configMapGenerator behavior in kustomization and typo fixes #551
🏃 Change configMapGenerator behavior in kustomization and typo fixes #551
Conversation
5be982b
to
012d0d8
Compare
/test-integration |
/cc @maelk |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: furkatgofurov7, maelk The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
What this PR does / why we need it:
This patch fixes configMapGenerator behavior so that when BMO is deployed as part of CAPM3 it needs to be able to
create
configmap rather thanmerge
and also addresses few fixes to some comments (typo and rephrasing) in #541Logs:
Error: accumulating resources: accumulateFile "accumulating resources from '../deploy/default': '/home/****/go/src/github.com/metal3-io/baremetal-operator/deploy/default' must resolve to a file", accumulateDirector: "recursed accumulation of path '/home/****/go/src/github.com/metal3-io/baremetal-operator/deploy/default': merging from generator &{0xc0007bb230 { } {{ ironic-bmo-configmap merge {[] [] [ironic_bmo_configmap.env]} <nil>}}}: id resid.ResId{Gvk:resid.Gvk{Group:\"\", Version:\"v1\", Kind:\"ConfigMap\"}, Name:\"ironic-bmo-configmap\", Namespace:\"\"} does not exist; cannot merge or replace"
Related to: /metal3-dev-env/pull/338