Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

genesis new with S3 blobstore access key #112

Open
michaelmccaskill opened this issue Dec 17, 2020 · 1 comment
Open

genesis new with S3 blobstore access key #112

michaelmccaskill opened this issue Dec 17, 2020 · 1 comment
Assignees
Labels
PRIORITY: High Work-around problematic for core functionality, or no workaround for secondary functionality TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Bug Defect in intended behaviour
Milestone

Comments

@michaelmccaskill
Copy link
Contributor

  • Genesis 2.7.26
  • Kit 2.0.1

Using the new hook, I enabled S3 blobstore and entered my credentials. However, the access key in Vault is empty.

 safe get secret/cf/lab/aws/ue1/sandbox/bosh/blobstore/s3
--- # secret/cf/lab/aws/ue1/sandbox/bosh/blobstore/s3
access_key: ""
secret_key: <REDACTED>

Resulting env file

kit:
  name:    bosh
  version: 2.0.1
  features:
    - aws
    - s3-blobstore
    - bosh-dns-healthcheck
    - netop-access

genesis:
  env:                cf-lab-aws-ue1-sandbox
  bosh_env:           cf-lap-ops
  min_version:        2.7.8


params:
  # These parameters are all that we need to specify for an Environment
  # BOSH, since networking and VM type configuration comes from that cloud-config
  #
  static_ip: 10.175.23.36

  # BOSH on AWS needs to know what region to deploy to, and what
  # default security groups to apply to all VMs by default.
  #
  # AWS credentials are stored in the Vault at
  #   /secret/cf/lab/aws/ue1/sandbox/bosh/aws
  #
  aws_region: us-east-1
  aws_default_sgs:
    - Main-Sandbox-vms

  # External S3 Blobstore Configuration
  s3_blobstore_bucket: main-sandbox-bosh
  s3_blobstore_region: us-east-1

  # DNS Caching (for runtime config)
  dns_cache: true
@bodymindarts
Copy link
Contributor

This is strange... I could see in the code that only access_key was being persisted in vault and created a PR: #116 for that.
But in your console output its exactly the other way around secret_key is there (it shouldn't be) and access_key is empty.

@dennisjbell dennisjbell added PRIORITY: High Work-around problematic for core functionality, or no workaround for secondary functionality TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Bug Defect in intended behaviour labels Feb 11, 2021
@dennisjbell dennisjbell added this to the bosh-v2.0.2 milestone Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PRIORITY: High Work-around problematic for core functionality, or no workaround for secondary functionality TRIAGE: Accepted Ticket has been accepted for work to proceed TYPE: Bug Defect in intended behaviour
Projects
None yet
Development

No branches or pull requests

3 participants