Browse Source

Changing the self-host workflow s3 bucket name to use a secret and not use the bucket name. (#163)

* Changing the bucketname to use a secret to pull the bucketname and not use the real name of the bucket

* Adding the secret under Retrieve Secrets
pull/167/head
Josh Jordan 2 years ago committed by GitHub
parent
commit
dd9c7e8d77
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 5
      .github/workflows/release.yml

5
.github/workflows/release.yml

@ -116,6 +116,7 @@ jobs: @@ -116,6 +116,7 @@ jobs:
keyvault: "bitwarden-ci"
secrets: "aws-selfhost-version-access-id,
aws-selfhost-version-access-key,
aws-selfhost-version-bucket-name,
r2-electron-access-id,
r2-electron-access-key,
r2-bitwarden-selfhost-version-bucket-name,
@ -126,8 +127,8 @@ jobs: @@ -126,8 +127,8 @@ jobs:
env:
AWS_ACCESS_KEY_ID: ${{ steps.retrieve-secrets.outputs.aws-selfhost-version-access-id }}
AWS_SECRET_ACCESS_KEY: ${{ steps.retrieve-secrets.outputs.aws-selfhost-version-access-key }}
AWS_DEFAULT_REGION: 'us-west-2'
AWS_S3_BUCKET_NAME: 's3://public-s3-bitwarden-selfhost-version-artifact'
AWS_DEFAULT_REGION: 'us-east-1'
AWS_S3_BUCKET_NAME: ${{ steps.retrieve-secrets.outputs.aws-selfhost-version-bucket-name }}
run: |
aws s3 cp version.json $AWS_S3_BUCKET_NAME \
--acl "public-read" \

Loading…
Cancel
Save