Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private Connection data sources not available in v0.6.0 #595

Closed
4 tasks done
joelsdc opened this issue Mar 1, 2023 · 5 comments · Fixed by #659
Closed
4 tasks done

Private Connection data sources not available in v0.6.0 #595

joelsdc opened this issue Mar 1, 2023 · 5 comments · Fixed by #659
Labels
bug Something isn't working

Comments

@joelsdc
Copy link

joelsdc commented Mar 1, 2023

Readiness Checklist

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed
  • I am reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior

The ec_gcp_private_service_connect_endpoint datasource to work

Current Behavior

│ Error: Invalid data source
│
│   on service_elastic.tf line 7, in data "ec_gcp_private_service_connect_endpoint" "default":
│    7: data "ec_gcp_private_service_connect_endpoint" "default" {
│
│ The provider elastic/ec does not support data source "ec_gcp_private_service_connect_endpoint".

Terraform definition:

As per documentation:

data "ec_gcp_private_service_connect_endpoint" "default" {
  region = "us-central1"
}

Steps to Reproduce

  1. Add a ec_gcp_private_service_connect_endpoint datasource
  2. Try to run terraform plan/apply

Context

After upgrading to v0.6.0 of the provider the ec_gcp_private_service_connect_endpoint datasource no longer works.
On v0.5.1 ec_gcp_private_service_connect_endpoint works correctly.

Your Environment

  • Version used: v0.6.0
  • Terraform cli: v1.3.9
@joelsdc joelsdc added the bug Something isn't working label Mar 1, 2023
@joelsdc
Copy link
Author

joelsdc commented Mar 1, 2023

Looking at the diff between v0.5.1 and v0.6.0 I have the feeling that all private-link datasources are broken...

@joelsdc
Copy link
Author

joelsdc commented Mar 2, 2023

@tobio tagging you.

@tobio
Copy link
Member

tobio commented Mar 2, 2023

@joelsdc sorry about the frustration here. tl;dr I'd stick with 0.5.1 until there's a follow up release here.

It's expected that the ec_gcp_private_service_connect_endpoint, ec_aws_privatelink_endpoint, and ec_azure_privatelink_endpoint data sources aren't available in 0.6. The release notes indicate that changes made in 0.5x are not expected to be part of 0.6, however we can definitely be more explicit about what's missing. I'll chase this up.

At some point during the development of the migration to the TF plugin framework (i.e the 0.6.0 release) it was decided to perform a wholesale migration based on the 0.4 branch, and follow up with the 0.5 changes in a later release. The result is a pretty frustrating user experience, I understand this is far from ideal for you right now.

@dimuon is there work underway to migrate the private link data sources (along with the other 0.5x changes) in a 0.6.1 release? Do we have a timeframe here?

I have the feeling that all datasources are broken

@dimuon are you able to take a look into this. FWIW the ec_stack is working for me in 0.6.0

@joelsdc
Copy link
Author

joelsdc commented Mar 2, 2023

Thanks @tobio for checking this, I'm editing my comment from above, I was referring to all private-connection data sources (meaning GCP, AWS and Azure). I myself should have been more specific.

My recommendation, until the data sources are ported to the 0.6 branch, would be to:

1- Remove them from the docs: https://registry.terraform.io/providers/elastic/ec/latest/docs

image

2- Make it crystal clear in the README / CHANGELOG / etc that they are not available.

I know it's mentioned in the changelog that "0.6 is based on 0.4 and changes added in 0.5 are not available in 0.6", so that leaves it to the user of the provider to go figure out what was added in 0.5 to know it's not available in 0.6, but then the 0.6 documentation says otherwise, which one is the source of truth?

I'm going to stick to 0.5 until this is solved so stay tuned for more bug reports ;)

@joelsdc joelsdc changed the title v0.6.0 breaks GCP installations -> The provider elastic/ec does not support data source "ec_gcp_private_service_connect_endpoint". Private Connection data sources not available in v0.6.0 Mar 2, 2023
@dimuon
Copy link
Contributor

dimuon commented Mar 7, 2023

@tobio, I'm sorry for the late response - I was on PTO.
ec_stack works for me as well.

Regarding a time frame for migrating the private link data sources, I think @Kushmaro can provide more information on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants