Skip to content
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

E2E BTP Manager secret customization test #935

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

szwedm
Copy link
Contributor

@szwedm szwedm commented Dec 19, 2024

Description

Changes proposed in this pull request:

Add e2e test for BTP Manager secret customization. See the test proposal for the test flow overview.

Related issue(s)

Closes #921

@szwedm szwedm added the kind/enhancement Categorizes issue or PR as related to modifying or improving an existing feature label Dec 19, 2024
@szwedm szwedm self-assigned this Dec 19, 2024
@kyma-bot kyma-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cla: yes Indicates the PR's author has signed the CLA. labels Dec 19, 2024
Copy link

Add one of following labels

- kind/feature -> Use it when you want to submit a new feature

- kind/enhancement -> Use it when you modify or improve an existing feature

- kind/bug -> Use it when you fix a bug

@kyma-bot kyma-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 19, 2024
@kyma-bot kyma-bot added the area/documentation Issues or PRs related to documentation label Dec 20, 2024
@szwedm szwedm marked this pull request as ready for review December 20, 2024 14:57
@szwedm szwedm requested review from a team as code owners December 20, 2024 14:57
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 20, 2024
@kyma-gopher-bot kyma-gopher-bot enabled auto-merge (squash) December 20, 2024 14:57
@MarekMichali
Copy link
Contributor

MarekMichali commented Dec 23, 2024

Keep in mind that you won't be able to merge it, because by default All checks passed treats every job as a required to pass. If you want, you can add this job to be skipped in All checks passed config.

@jaroslaw-pieszka jaroslaw-pieszka self-requested a review December 23, 2024 11:18
SAP_BTP_OPERATOR_CONFIGMAP_RESOURCE_VERSION=$(kubectl get configmap -n ${NAMESPACE} ${SAP_BTP_OPERATOR_CONFIGMAP_NAME} -o jsonpath="{.metadata.resourceVersion}")

## Save current ID of the resource to be recreated
SAP_BTP_OPERATOR_CLUSTER_ID_SECRET_ID=$(kubectl get secret -n ${NAMESPACE} ${SAP_BTP_OPERATOR_CLUSTER_ID_SECRET_NAME} -o jsonpath="{.metadata.uid}")
Copy link
Contributor

@jaroslaw-pieszka jaroslaw-pieszka Dec 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The secret that should be eventually re-created with a new cluster_id should be located in the $MANAGEMENT_NAMESPACE namespace.
Unless we do not change the namespace.

We need to double check the btp-operator behaviour. Possible this remark above is invalid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation cla: yes Indicates the PR's author has signed the CLA. kind/enhancement Categorizes issue or PR as related to modifying or improving an existing feature size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

End-to-end (e2e) integration test for customizing BTP Manager input secret
4 participants