Expired ECR authorization token causes state file change #424
Labels
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/enhancement
Improvements or new features
What happened?
When using ECR to store the docker image, a temporary token is used and stored in state.
The token expires after 12 hours.
So if a refresh is done after 12 hours, it can't query ECR and wants to remove the image from state.
This is a real problem for customers using Drift Detection schedules with deployments.
Example
pulumi refresh
and see that it's fine.pulumi refresh
and see the error above and it's desire to remove the image from state because it can't communicate with ECR.Output of
pulumi about
CLI
Version 3.147.0
Go Version go1.23.5
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.66.3
resource command 1.0.1
resource docker-build 0.0.9
language python 3.147.0
Host
OS darwin
Version 15.2
Arch x86_64
This project is written in python: executable='/Users/mitch/Downloads/wmg-dockerbuild-token-expiry/dockerbuild/venv/bin/python' version='3.11.8'
Current Stack: xxxxxx/docker-build-deploy/dev
TYPE URN
pulumi:pulumi:Stack urn:pulumi:dev::docker-build-deploy::pulumi:pulumi:Stack::docker-build-deploy-dev
pulumi:providers:aws urn:pulumi:dev::docker-build-deploy::pulumi:providers:aws::default_6_66_3
aws:ecr/repository:Repository urn:pulumi:dev::docker-build-deploy::aws:ecr/repository:Repository::refresh-ecr-repository
pulumi:providers:docker-build urn:pulumi:dev::docker-build-deploy::pulumi:providers:docker-build::default_0_0_9
docker-build:index:Image urn:pulumi:dev::docker-build-deploy::docker-build:index:Image::refresh_db_export_lambda_image
Found no pending operations associated with team-ce/dev
Backend
Name pulumi.com
Dependencies:
NAME VERSION
pulumi_aws 6.66.3
pulumi_command 1.0.1
pulumi_docker_build 0.0.9
setuptools 65.5.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: