You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems the plugin is designed to publish to multiple EB environments within a single EB application in a single AWS account. It's not obvious from looking at the sample beanstalk DSL block on the README how to handle multiple applications or accounts.
I assume it would be possible by using Groovy variables in the build file, but it would be better if there was a standard/documented way to do it with the DSL and standard beanstalk Gradle tasks.
The text was updated successfully, but these errors were encountered:
msgilligan
changed the title
Document how best to deploy to multiple AWS accounts
Document how best to deploy to multiple EB applications and/or AWS accounts
Aug 24, 2018
Right, it should be possible to create a new instance of the task and pass custom properties for that.
Unfortunately I've never tested that and I don't even have an active beanstalk environment right now since I've been working on other things for couple of years. So I'd gladly merge a PR for documenting this, but I'm afraid I won't do it myself for the foreseeable future.
It seems the plugin is designed to publish to multiple EB environments within a single EB application in a single AWS account. It's not obvious from looking at the sample
beanstalk
DSL block on the README how to handle multiple applications or accounts.I assume it would be possible by using Groovy variables in the build file, but it would be better if there was a standard/documented way to do it with the DSL and standard beanstalk Gradle tasks.
The text was updated successfully, but these errors were encountered: