In the past this has lead to build failures when credentials were updated in only one place.
This PR updates any credentials which are duplicated, migrating them to use the value directly from AWS Secrets Manager. The methodology on this logic is described here.
I'm confident from my testing the values will resolve correctly, but as the job is triggered on tag, I am unable to test in a non-destructive way.
I've also rescoped secrets.HZ_ENTERPRISE_LICENSE to reduce the cognitive complexity of looking through the actions' environment secrets.
Backport of https://github.com/hazelcast/hazelcast-docker/pull/812
Currently, credentials are duplicated between:
In the past this has lead to build failures when credentials were updated in only one place.
This PR updates any credentials which are duplicated, migrating them to use the value directly from AWS Secrets Manager. The methodology on this logic is described here.
I'm confident from my testing the values will resolve correctly, but as the job is triggered on
tag
, I am unable to test in a non-destructive way.I've also rescoped
secrets.HZ_ENTERPRISE_LICENSE
to reduce the cognitive complexity of looking through the actions' environment secrets.Fixes: DI-78