Skip to content

Update secrets to match those in Vault#75

Open
viccuad wants to merge 1 commit intomasterfrom
viccuad/upd-secrets
Open

Update secrets to match those in Vault#75
viccuad wants to merge 1 commit intomasterfrom
viccuad/upd-secrets

Conversation

@viccuad
Copy link
Member

@viccuad viccuad commented Nov 19, 2020

These changes update the pipeline code to match the renaming of secrets in concourse.suse.dev. This is needed to make secrets in Vault and concourse.suse.dev consistent.

@viccuad
Copy link
Member Author

viccuad commented Nov 19, 2020

Blocked by #74

@viccuad viccuad added the Blocked This issue or pull request is blocked by another one label Nov 19, 2020
bucket: {{ $config.s3minibroker.bucket }}
access_key_id: ((aws-cf-user-suse-rd.access-key))
secret_access_key: ((aws-cf-user-suse-rd.secret-key))
access_key_id: ((aws-access-key))
Copy link
Member

@prabalsharma prabalsharma Nov 20, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This won't work as this bucket is in suse-rd account and not our account. Unless, minibroker CI has moved the s3 bucket.

Copy link
Member Author

@viccuad viccuad Nov 25, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seems to be a mismatch between secret names in concourse.suse.de and concourse.suse.dev. One way to fix it was to do the change here and swap aws-access-key and aws-capbot-access-key values in concourse.suse.dev.

With the latest developments, seems we need to change the secrets layout in Vault so the Concourse instances can seamlessly pull them.

Copy link
Member

@prabalsharma prabalsharma Nov 26, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its confusing to name rd account creds as aws-access-key/secret-key. In black box we have a liberty to add comments but we don't have the same in k8s secrets.
I am okay with using aws-capbot-access-key/secret-key, but for rd account I guess we should stick to aws-cf-user-suse-rd.access-key/secret-key, for clarity.
Also, we have this issue right now with rd account https://jira.suse.com/browse/CAP-1655

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, the name is confusing, aws-cf-user-suse-rd.access-key/secret-key is a better name. But migrating all the pipelines and reflying them to consume it is not trivial (sometimes one has problems when flying some pipelines).
This would get solved automatically with cloudfoundry-incubator/kubecf#1607 or cloudfoundry-incubator/kubecf#1608, but maybe we just need to fix it apart from those cards.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@viccuad viccuad removed the Blocked This issue or pull request is blocked by another one label Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants