We could have situations where the lambda is deployed and then we would have to re-deploy to adjust CPU requests or Memory settings or instances of the Keycloak deployment.
Right now, when we attempt to do that, the deploy-route53-failover-lambda exits with a status code 254 indicating the role is already present. We should make this code path idempotent to be able to re-deploy even when the lambda is already created.
task: [deploy-route53-failover-lambda] DOMAIN=primary.gh-keycloak-a-gh-keycloak-b-nzixmqo.keycloak-benchmark.com ./route53_create_failover_lambda.sh
[deploy-route53-failover-lambda]
[deploy-route53-failover-lambda] An error occurred (EntityAlreadyExists) when calling the CreateRole operation: Role with name 963c6aea-869e-48b0-a900-b762a6d6a5fd already exists.
task: Failed to run task "default": exit status 254
Description
We could have situations where the lambda is deployed and then we would have to re-deploy to adjust CPU requests or Memory settings or instances of the Keycloak deployment.
Right now, when we attempt to do that, the
deploy-route53-failover-lambdaexits with a status code254indicating the role is already present. We should make this code path idempotent to be able to re-deploy even when the lambda is already created.Discussion
No response
Motivation
No response
Details
No response