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

Separate development and production environments #41

Closed
kikuomax opened this issue Sep 2, 2021 · 5 comments
Closed

Separate development and production environments #41

kikuomax opened this issue Sep 2, 2021 · 5 comments
Assignees

Comments

@kikuomax
Copy link
Member

kikuomax commented Sep 2, 2021

Once we release a product, we should not inattentively change it. So we need a isolated playground where we can continue development after a product is released.

Details

Development environment

Production environment

@kikuomax kikuomax self-assigned this Sep 2, 2021
@kikuomax
Copy link
Member Author

kikuomax commented Sep 2, 2021

We have to provision two copies of the following resources,

  • DynamoDB tables
  • Cognito user pool
  • APIs (because Cognito user pools are different)

We still can reuse Lambda functions if we carefully version them.

@kikuomax
Copy link
Member Author

kikuomax commented Sep 2, 2021

OK, let's start from deploying two copies of CDK stacks.

@kikuomax
Copy link
Member Author

kikuomax commented Sep 2, 2021

Give a context that determines development or production to the CDK stack.

@kikuomax
Copy link
Member Author

kikuomax commented Sep 2, 2021

Give a context that determines development or production stage to the CDK stack.

We want to change stack name by the designated stage. Can we get a context before creating a Stack instance?

Yes, use an App instance.

@kikuomax
Copy link
Member Author

This issue is no longer relevant as we start over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant