Remove obsolete L2/L3 operator bindings from provisioner #3438
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kyma-bot
added
cla: yes
koala7659
requested changes
May 20, 2024
components/provisioner/internal/operations/stages/provisioning/create_operators_bindings.go
Outdated
Show resolved
Hide resolved
...onents/provisioner/internal/operations/stages/provisioning/create_operators_bindings_test.go
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The L2 and L3 operator bindings were for a legacy (OIDC based) approach to authorize SAP operator access to SKRs, but are not needed any more.
After this PR is merged, I plan to raise another PR to remove related code from kcp chart.
Related issue(s)
https://github.tools.sap/kyma/backlog/issues/5553