It is possible to override many other properties, e.g. -Ddeployment.stage=alpha.
However, when overriding bucket with -Ddeployment.bucket=lambda-deploy-bogus the deploy module will respect the override but the cloudformation activities will not.
org.lambadaframework.deployer.Deployment.java seems to get most parameters via constructor but it determines the bucket in some other way. Is there a particular reason for that?
It is important when a group of developers are collaborating and running tests on their individual AWS accounts.
It is possible to override many other properties, e.g.
-Ddeployment.stage=alpha.However, when overriding bucket with
-Ddeployment.bucket=lambda-deploy-bogusthe deploy module will respect the override but the cloudformation activities will not.org.lambadaframework.deployer.Deployment.java seems to get most parameters via constructor but it determines the bucket in some other way. Is there a particular reason for that?
It is important when a group of developers are collaborating and running tests on their individual AWS accounts.