-
Notifications
You must be signed in to change notification settings - Fork 18
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
base: main
Are you sure you want to change the base?
E2E BTP Manager secret customization test #935
Conversation
Add one of following labels |
Keep in mind that you won't be able to merge it, because by default |
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}") |
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.
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.
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