Skip to content
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.

Using temporary credentials for initial deployment breaks self-updates #30

Open
jpluscplusm opened this issue Jan 16, 2018 · 1 comment

Comments

@jpluscplusm
Copy link
Contributor

The self-updating pipeline has its AWS creds baked in from the initial CLI invocation of concourse-up. If these creds were issued by a aws sts assume-role or equivalent, then the concourse-up-self-update job fails, as the credentials expire a maximum of 60 minutes after creation.

Perhaps an additional self-update IAM user could be created during deployment. This might be possible to make optional - I believe it's possible to discover if the context you're operating in (as Terraform, etc) is based on temporary creds.

@danyoung
Copy link
Contributor

danyoung commented Jan 16, 2018

Nice catch Jon. I've created a placeholder story for this feature request here https://www.pivotaltracker.com/story/show/155699858

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants