Managing per deployment stage (e.g. prod, dev) configuration using CDK?

0

We're migrating from Serverless Framework (SF) to CDK and I'm wondering how to best manage per deployment stage (e.g. prod, dev) configuration using CDK. IN SF we had a YAML block like this:

  prod:
    alertsEmail: alerts@ourdomain.com
    captchaSecretId: prod/Backend/CaptchaSecretId
    enableAlarms: true
    enableDashboards: true

  dev:
    alertsEmail: dev-alerts@ourdomain.com
    captchaSecretId: prod/Backend/CaptchaSecretId
    enableAlarms: false
    enableDashboards: false

  default:
    # ...

("default" was used for all other stacks, like the per-developer sandbox stacks.)

These configuration variables then affect how we set up our CloudFormation (CF) resources. For example, if enableAlarms is true we'd add a bunch of Alarm resources.

  • What's the recommended way to store per deployment stage configuration?
  • How do we best specify which environment we're in when deploying? Using SF we'd do serverless deploy --stage=prod and the configuration got pick using the --stage command line flag.
  • please accept the answer if it was useful

tibbe
asked 22 days ago195 views
1 Answer
1
profile picture
EXPERT
answered 22 days ago
profile picture
EXPERT
Artem
reviewed 19 days ago
profile pictureAWS
EXPERT
reviewed 21 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions