How to set Marvel license programmatically in Ansible deploy?

We have a license for Marvel and while the documentation just says to enter
it through the Marvel UI when prompted, we script 100% of our
infrastructure creation and deployments (Ansible). My goal is to be able to
start with a bare VM, run our deployment, and when the dust settles, our
production Marvel cluster should have its license activated, and our
development/test clusters should be registered in development mode.

I've got to believe this is possible but I've looked everywhere but can't
find any instructions on how to do this, so any guidance would be greatly
appreciated.

Thanks!

-joel

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Unfortunately there isn't a way to do this, but I've raised a feature
request to get this added.

On 30 April 2015 at 23:39, Joel Potischman joel.potischman@beatport.com
wrote:

We have a license for Marvel and while the documentation just says to
enter it through the Marvel UI when prompted, we script 100% of our
infrastructure creation and deployments (Ansible). My goal is to be able to
start with a bare VM, run our deployment, and when the dust settles, our
production Marvel cluster should have its license activated, and our
development/test clusters should be registered in development mode.

I've got to believe this is possible but I've looked everywhere but can't
find any instructions on how to do this, so any guidance would be greatly
appreciated.

Thanks!

-joel

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9TR%3DQ8spVifdFHVtrpmzvszWwURkDuNdqYcaXHFmVG_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Just to add, the shield repo isn't publically accessible do to it being one
of our commercial plugins, so I can't link you to the issue sorry!

On 1 May 2015 at 07:37, Mark Walkom markwalkom@gmail.com wrote:

Unfortunately there isn't a way to do this, but I've raised a feature
request to get this added.

On 30 April 2015 at 23:39, Joel Potischman joel.potischman@beatport.com
wrote:

We have a license for Marvel and while the documentation just says to
enter it through the Marvel UI when prompted, we script 100% of our
infrastructure creation and deployments (Ansible). My goal is to be able to
start with a bare VM, run our deployment, and when the dust settles, our
production Marvel cluster should have its license activated, and our
development/test clusters should be registered in development mode.

I've got to believe this is possible but I've looked everywhere but can't
find any instructions on how to do this, so any guidance would be greatly
appreciated.

Thanks!

-joel

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X--fBRF7me%2Bbz8xZ%3DS_wj6zR2%2BPaqa5a7FD2Yrr73AMXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Oh well. At least I now have a definitive answer. Thanks!

-joel

On Thursday, April 30, 2015 at 5:37:40 PM UTC-4, Mark Walkom wrote:

Unfortunately there isn't a way to do this, but I've raised a feature
request to get this added.

On 30 April 2015 at 23:39, Joel Potischman <joel.po...@beatport.com
<javascript:>> wrote:

We have a license for Marvel and while the documentation just says to
enter it through the Marvel UI when prompted, we script 100% of our
infrastructure creation and deployments (Ansible). My goal is to be able to
start with a bare VM, run our deployment, and when the dust settles, our
production Marvel cluster should have its license activated, and our
development/test clusters should be registered in development mode.

I've got to believe this is possible but I've looked everywhere but can't
find any instructions on how to do this, so any guidance would be greatly
appreciated.

Thanks!

-joel

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/02607a33-591b-4abf-95a7-3de475be406f%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/146a3aa5-7231-43ce-b26b-cc1ad2e48c04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.