Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions cap-ci/pipeline.yaml.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,8 @@ resources:
type: s3
source:
bucket: {{ $config.s3.bucket }}
access_key_id: ((aws-access-key))
secret_access_key: ((aws-secret-key))
access_key_id: ((aws-capbot-access-key))
secret_access_key: ((aws-capbot-secret-key))
regexp: {{ $config.s3.regexp }}
region_name: {{ $config.s3.region }}

Expand All @@ -73,8 +73,8 @@ resources:
type: s3
source:
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.

secret_access_key: ((aws-secret-key))
regexp: {{ $config.s3minibroker.regexp }}
region_name: {{ $config.s3minibroker.region }}

Expand All @@ -90,8 +90,8 @@ resources:
type: s3
source:
bucket: kubecf-klog
access_key_id: ((aws-access-key))
secret_access_key: ((aws-secret-key))
access_key_id: ((aws-capbot-access-key))
secret_access_key: ((aws-capbot-secret-key))
regexp: klog-(.*)\.tar\.gz$
region_name: us-west-2
endpoint: null
Expand Down