`genesis new` with S3 blobstore access key

[michaelmccaskill]

• 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]

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.