alma-cdk / project Goto Github PK

The plan is to support at least following CDK languages:

• Python (pip)
• Java (maven)
• Go (github)

The additional publish mechanism for additional languages will be implemented once this package is close to v1 release.

If a project has both account- and environment-scoped stacks and environment context variable is given to cdk, account-scoped (created in AccountWrapper) stacks' names change to contain environment too. This should not happen, and it should be possible to deploy both stacks with single command giving both account and environment context variables.

Few people have requested more flexible account configuration options, such as:

• multiple "dev" type of accounts
• more complex configuration on which environments can live in which accounts

We should definitely support this. Internally this shouldn't be too big change, as internally there already is a concept of "account type label".

We might combine this feature request to be part of internal refactor we've considered for some time.

We're using NestedStacks and would like to use the same naming convention for them. Currently we're using our own naming function but it would be so much better to use the Name.stack method for the same naming across the board.

When using AccountStrategy (one/two/three) configuration for Project, conceptually we can determine the target account just from the target environment.

Some relativy small refactor/rewrite is required to enable this.