Hi,

Currently the plugin ws.Cloud allows to use an external ID when doing an assume role.

We would also need it to be available on the k8s.Master CI

Without this, any project would be able to deploy anywhere. (the external ID would act as secret known only by the project configuring the infra ci)

Thank you

Comments

  • Thank you for sharing your idea. We would need more details on your use case, including the specific attributes, configurations, and processes you are looking for when handling secrets within Deploy or an external service.

  • Hi,
    Please ignore the secret part.
    The requirement is to be able to use an external ID on the k8s.Master CI when assuming a AWS role, just like its available for aws.Cloud

  • We'd like to have a discovery call on this use case and have asked the Field team to coordinate a call with our Product team.

  • This change will be available in 25.3 version.