Closed hikeeba closed 1 month ago
Also, are you open to pull requests from other parties?
Hey, appreciate the questions:
Do you expect this project/package to be expanded and supported for a while?
100% This is not a short-term project and I hope that it becomes a strong contender to AWS CDK Pipelines
What is the recommended pattern for handling multiple development/deployment environments (dev, test, staging, prod, etc.)?
This is how I approach it, have a look at the "Configuration" and "Multiple environments" sections on this post I wrote: https://rehanvdm.com/blog/aws-cdk-starter-configuration-multiple-environments-cicd (here is the attached GH repo for that: https://github.com/rehanvdm/cdk-starter).
Basically, I like to create an EnvironmentConfig
then and make a file for each environment config, like config/development.ts
. Then in the CDK app select the correct environment config file depending on a Context Variable (-c
).
Assuming there is a pattern for multiple environments, is there also a pattern for passing configuration values per environment?
Similar to the above, it leverages the CDK functionality, this package of mine is just a wrapper to improve the order of deployment for CDK stacks. So yes, if you can do it CDK then you can do it here as well.
Also, are you open to pull requests from other parties?
😃 YES, please! I see I don't have a CONTRIBUTING.md file. Just open an Issue first, then we can see if there are no one else working on it and I could give some tips. We then discuss ans assign it to you and you can start.
Perfect, thanks! We can close this issue and I'll try out the patterns mentioned in your post.
Just tested out this package and it looks very promising. Couple of questions if you have a moment.
Thanks so much!