Fix merging Kubernetes configuration #1253
Merged
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.
Description
Changes proposed in this pull request:
range
, but unfortunately, none were able to catch this because we are passing that pointer to a function. Evenrevive
.It's a valid candidate for cherry-picking into v1.4.1 release.
Testing
Unit tests
Writing manual compare was too slow, so first I used
but this was not producing readable enough assets, so I decided to go with YAML, but for that I had to export fields. Because the struct is still private, it doesn't change anything.
Manual
k3d cluster create
PLUGIN_TARGETS="kubernetes" make build-plugins-single
env PLUGIN_SERVER_HOST=http://host.k3d.internal go run test/helpers/plugin_server.go
env BOTKUBE_CONFIG_PATHS="./helm/botkube/values.yaml,/tmp/debug-events.yaml" go run ./cmd/botkube-agent/main.go
gitlab-runner
ns and delete it, create configmap indefault
ns and try to delete it.Related issue(s)
#1251