36 lines
1.4 KiB
Plaintext
36 lines
1.4 KiB
Plaintext
# this config file is useful if you don't want to run vault
|
|
# agents with canvas. Local Development is the most common case
|
|
# for this, but a small OSS deployment might have it make sense too.
|
|
# Just provide the results data you want the Vault class to "read",
|
|
# and it will return it when a call for vault data is issued. Data should be
|
|
# shaped like the example below. Each environment can get a hash,
|
|
# there's a key for each read path, and a hash for the returned data
|
|
development:
|
|
'sts/testaccount/sts/canvas-shards-lookupper-dev':
|
|
access_key: 'fake-access-key'
|
|
secret_key: 'fake-secret-key'
|
|
security_token: 'fake-security-token'
|
|
'sts/testaccount/sts/canvas-release-notes':
|
|
access_key: 'fake-access-key'
|
|
secret_key: 'fake-secret-key'
|
|
security_token: 'fake-security-token'
|
|
# 'app-canvas/data/secrets':
|
|
# data:
|
|
# google_docs_creds:
|
|
# secret_key: so-secret
|
|
# inst_access_signature:
|
|
# private_key: <private key in base 64>
|
|
# encryption_public_key: <public key in base 64 [NOT SAME KEYPAIR AS SIGNATURE!]>
|
|
# sentry_dsn: garbage-dsn-here
|
|
# twilio_creds:
|
|
# account_sid: <sid>
|
|
# auth_token: <token>
|
|
# twitter_creds:
|
|
# api_key: <apikey>
|
|
# secret_key: <secretkey>
|
|
test:
|
|
'sts/testaccount/sts/canvas-shards-lookupper-test':
|
|
access_key: 'fake-access-key'
|
|
secret_key: 'fake-secret-key'
|
|
security_token: 'fake-security-token'
|