v2.1.2

Added

• New export VEDA_COGNITO_DOMAIN duplicates existing export with key expected for downstream applications.

v2.1.1

Added

• Adds aws_region to each stored client secret

Fixed

• Fixes The Outputs section contains duplicate Export names by making client secret id export names unique (and more specific). New export names are:
  • {stack_name}-workflows-client-secret-id for the service client secret used by airflow
  • {stack_name}-programmatic-client-secret-id for the use password token generating client used for endpoints that grant tokens (ingest-api, maybe workflows-api in future)
  • {stack_name}-identity-provider-secret-id for the optional data managers group (not used in higher environments)
• cicd pr and deployment actions on main branch now triggers cdk diff and deployment on a stack named veda-auth-stack-staging

v2.0.0

Changes

CICD

• Add composite action to be used by veda-deploy
• Update cicd to use the composite action
• Add gitflow enforcer
• Add CfnOutput to pass env vars between stacks in veda-deploy
• Cicd.yml simplified (for now) to automatically deploy on dev and main branches. In the future we may want to implement the pattern of calling the cdk-actions/workflow that is used for production for the lower environments as well but today the lower environment aws setup lacks the appropriate deployment role

Upgrades

• Upgrade to latest aws-cdk version https://github.com/aws/aws-cdk/releases?q=node&expanded=true to use latest node runtime version for AwsCustomResource https://github.com/NASA-IMPACT/veda-auth/blob/main/infra/stack.py#L176-L199
• Updated aws-cdk version requires additional cdk context "@aws-cdk/customresources:installLatestAwsSdkDefault": false

Breaking changes

• Stop creating an additional duplicate values with veda_ in keys client aws secrets manager (no longer required for downstream deployment)

v1.0.0

First semantic release version