Provider releases not available in the Terraform registry #173
Comments
|
Hey @felixlut, I'm not sure why it's not showing up on releases.hashicorp.com but it is appearing on the registry here. I'll open a support ticket with Hashicorp to get some more information. Additionally, I can confirm that our customers are using versions newer than |
|
@ldhenry Thanks for the swift replies the last couple of days, it's been great! Yes I'm very confused on the matter as well, since I too have been using 2.13.x when playing around with it. I noticed when I was looking at the github-provider that the hasicorp releases page for that one is up to date, so there is something weird here. Hopefully their support can shed some light on the matter 😃 |
|
I can see that we changed our signing key 5 months ago which seems to align with the timing of the 2.9.5 release. I have sent an email to hashicorp for help on this. |
|
@ldhenry any update on this? |
Sorry, I bumped the support issue last Friday and still haven't heard anything. |
|
Hey @felixlut, Sorry for the long delay on this. I've been in touch with our partner at Hashicorp and have been told that releases.hashicorp.com is only used by older versions of Terraform (I believe pre-0.13 but I will confirm). For this reason, they did not recommend that we move forward with trying to get new releases of the LaunchDarkly Terraform provider on releases.hashicorp.com. I'll leave this issue open until I can get a confirmation on what versions of Terraform will no longer be compatible with the latest versions of the LaunchDarkly Terraform provider. Thanks, |
|
Hey @ldhenry. No issues, we found a workaround by using the GitHub releases in this repo directly instead. |
|
That's great to hear! |
Hey!
Going to the official Terraform registry, I cannot see the latest releases of this provider (last one is
2.9.5). Did you change anything in your release process since then?Once again, related to trying out #170 😄
The text was updated successfully, but these errors were encountered: