How do people rotate their tokens in thrird-party services?

Hi Raphael 👋 While not yet documented, we have recently included support for random password and passphrase rotators which can help to support secrets rotation on services not natively supported by ESC. You can use the

table view

select

rotator config

and then

memorable passphrase

or

random passsword

as rotator. Also, from the

Document View

fn::rotate::password:
      inputs:
        overrideSpecial: "!@#$%&*()-_=+[]{}<>:;"
        minSpecial: 4
        minUpper: 3
        minLower: 2
        length: 15

fn::rotate::passphrase:
      inputs:
        capitalize: true
        length: 4

Do I understand it correctly, that this applies to passwords generated by ESC?

This does apply to passwards managed by ESC. Is your question how do you rotate secrets owned by third parties such as other Saas? Each of those services has their own mechanism, sometimes they allow for automation and sometimes they allow only manual rotation. If the service allows for automated rotation and you would like us to consider integrating, please feel free to add a ticket here.

Yes, I'm talking about tokens generated by third party services. I have about 20

secure

entries in my Pulumi.$stack.yaml, mostly tokens generated by third-party services, and it's a small company. A few of them requires regular rotation, but anyway all of them should be rotated, and most of them has an API for it. The only thing I found is keydra, but it doesn't look like it has any adoption or repo traffic