ingenieux/beanstalker

Passing environment variables during Environment creation

Closed this issue · 6 comments

cemo commented

Hi,

Is it possible to add documentation regarding how to add environment variables during environment creation.

Thanks

Are we talking about this guy, right?

http://beanstalker.ingenieux.com.br/beanstalk-maven-plugin/create-environment-mojo.html#optionSettings

optionSettings:

Configuration Option Settings. Will evaluate as such:

If empty, will lookup for beanstalk.env.aws.x.y variable in the context, and it will map this variable to
namespace [aws.x], under option name y, unless there's an alias set.

cemo commented
<optionSetting>
   <optionName>beanstalk.env.CEMO_VARIABLE</optionName>
   <value>DEMO</value>
</optionSetting>

Will this create a variable CEMO_VARIABLE with value DEMO? Or could you help me please?

Shortest path (not sure, I need to review), ref: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-docker-elasticbeanstalkapplicationenvironment

<properties>
  <beanstalk.env.aws.elasticbeanstalk.application.environment.CEMO_VARIABLE>DEMO</beanstalk.env.aws.elasticbeanstalk.application.environment.CEMO_VARIABLE>
</properties>

If you've got an existing env, dump-properties might help you:

http://docs.ingenieux.com.br/project/beanstalker/managing-environments.html

cemo commented

dump-properties is nice. <3

So, how did it end up? How did you solve it?

cemo commented

I first declared a property and then used dump-properties. I used as in the same way in the output and it worked.

But I am not sure whether it is working by put environment or not. But It worked with create.