Not possible to read custom endpoint alias

[dangbert]

Overview

I'd like to read a more human readable endpoint URL from my terrafom resource, at the moment it seems we can only read ec_deployment.this.elasticsearch.https_endpoint which is the ugly form of the URL.

Possible Implementation

Testing

Context

I'm importing my team's elastic cloud deployment into terraform. We previously passed the endpoint URL via a terraform variable so other terraform resources could read it. Now that I'm using a ec_deployment terraform resource, reading ec_deployment.this.elasticsearch.https_endpoint docs here will result in a non-empty terraform plan (for our other resources that depend on this URL) after my refactor as the endpoint URL is changing. I'd also like the team to be able to see the cleaner endpoint URL in our terraform output.

I could construct the URL myself using the alias and region etc, but it seems janky and I wouldn't trust it to not change long term personally.

Your Environment

Macbook Pro M1, nothing special

[mark-adams]

I'm also experiencing the same issue. It'd be great to have a read-only aliased_url property on both the resource and the data source.

[GeorgeGkinis]

@mark-adams I also just stumbled upon this.

I also see you committed some changes.
When do you think that a pull request could be created?