Gavin Williams

@Crapworks I've had a quick look, and currently Gophercloud doesn't support FWaaS v2. Therefore support will need to be added to Gophercloud before we can add support into TF.

> When Elasticsearch is installed with a custom service_name, puppet will fail because the custom name is not used for the before relationship metaparameter. I'd also be interested to understand...

> > I'd also be interested to understand the purpose behind changing the service name. With the recent removal of multi-instance support in the 7.x module release, we're trying to...

> The only reason was that we always named the service elasticsearch-default. So it has no impact for us if the service name cannot be changed anymore. Thanks for confirming...

Hi there, Firstly, thank you for taking the time to contribute, and apologies for the radio silence from Elastic on this PR. I'm going to be working on this module...

@lucabelluccini Thank you for taking the time to dive into this issue and PR. I've labelled it as `wontfix` currently, as part of the updates of this module for Elasticsearch...

Firstly, thank you to everyone who has taken the time to provide feedback, 👍's etc, and apologies for not updating sooner. In the background, we've been working on resolving some...

> Please ensure support for upgrading from 6.x to 7.x for instances that were installed using this module. @zofog We will be working to make the upgrade and migration path...

> Are You planning to remove that when dealing with the multi instance part of the module? > > If so, do You have any examples of how we have...

Hey there, Firstly, apologies for the radio silence on this issue. The good news is that the `master` branch now supports deploying Elasticsearch 7.x!!! So if you feel up for...