Version 0.5.2 Release

[TrueTechy]

Hi there, I was looking to see if there's a planned release coming. I recently started using the provider and it's been great, had to compile from master to get that last commit about contact sorting but getting it to play nicely with terraform across OSes is not fun.

Thanks for all the great work you guys are doing here

[matteodepalo]

I'm in the same boat, stuck with the old version and with my runs on Terraform Cloud full of unrelated changes. I couldn't find an easy way to use a provider from GitHub unfortunately. @TrueTechy did you publish your own provider?

[TrueTechy]

I built the provider locally and just used that one instead, never published it though. I'm not sure if that's an option for you using terraform cloud

[dlecan]

@louy any chance to see a new release soon? Do you need help?

[kevinburke1]

I looked at creating a fork and releasing that, unfortunately it's not just as easy as updating the username in the "required_providers" list, apparently.

│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider meterup/uptimerobot: provider registry registry.terraform.io does not have a provider named registry.terraform.io/meterup/uptimerobot
│
│ All modules should specify their required_providers so that external consumers will get the correct providers when using a module. To see which modules are currently depending on meterup/uptimerobot,
│ run the following command:
│     terraform providers

[gmile]

From our side, there's interest in having the new code released too. We're particularly interested in having ability to specify Telegram #94 as a contact, since SMS is currently out of reach #98

[TrueTechy]

So the docs on publishing your own provider turned out to be really well done, so good job hashicorp. I've taken a fork of the repository and published master as v0.5.2 which you can find at https://registry.terraform.io/providers/TrueTechy/uptimerobot Hopefully this works for others, it worked fine on ours.

I did have to do a terraform state replace-provider for it to work on ours, but if that's just because I had been using a local version I'm not sure. Either way I hope this helps some people until the offical v0.5.2 is released

[johanfleury]

@TrueTechy do you plan on maintaining this fork?

[TrueTechy]

My main goal here was really to allow people to use the latest fixes in their transform projects. I'm more than happy to update the fork in line with this repo as releases are made. As for improvements, I've got minimal go experience at best so I'm not sure how useful I'd be at making any changes of my own to it.

[mnaser]

Hi @louy -- I understand that you might have been pretty busy with other things at hand, but do you think you'd be able to push out a release (or perhaps some of the previous contributors could get access to be able to create releases?)

It's a super useful utility for us and we'd love to be able to help at least maintain it by publishing new releases with the more recent fixes, reviewing code changes and getting darwin_arm64 builds going.

[mnaser]

Since there has been a lack of activity for the past few months and the lack of darwin/amd64 is breaking our workflows, we've gone ahead and forked the project here:

https://github.com/vexxhost/terraform-provider-uptimerobot

We're happy to continue to maintain the project, we've done a few things such as refactor for new docs format, and make it more in-line with the scaffolding repository, fixed the acceptance tests and connected it to our paid account to ensure we run acceptance tests all the time. It's also published to the registry here:

https://registry.terraform.io/providers/vexxhost/uptimerobot