No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I switched some helm charts deployed with `helm.v3.Release` to a private OCI repository, with the login (grabbed via `aws.ecr.getCredentialsOutput`) specified in `repositoryOpts`. The token it was deployed with has now expired, and it doesn't seem to want a request a new token or use the ambient credentials that the helm client is logged in with, so it's failing with a 403 when sending requests to the repo.

Is there a workaround for this?

edit: Managed to work around it by reverting back to the public charts. Think I'm going to avoid using private OCI repos with helm for now...