search

nebari-dev / nebari

🪴 Nebari - your open source data science platform
https://nebari.dev
BSD 3-Clause "New" or "Revised" License
282 stars 93 forks source link

Upgrade Terraform provider versions #2449

Open marcelovilla opened 6 months ago

marcelovilla commented 6 months ago

Context

Currently, we are using the following Terraform provider versions:

Provider Current version Current version release date Latest version Latest version release date
digitalocean/digitalocean 2.29.0 2023-07-17 2.38.0 2024-05-03
gavinbunney/kubectl 1.7.0 2020-09-18 1.14.0 2022-03-24
hashicorp/aws 5.33.0 2024-01-18 5.48.0 2024-05-02
hashicorp/azurerm 3.97.1 2024-03-22 3.102.0 2024-05-02
hashicorp/google 4.8.0 2023-08-28 5.28.0 2024-05-06
hashicorp/helm 2.1.2 2021-04-27 2.13.1 2024-04-15
hashicorp/kubernetes 2.20.0 2023-04-20 2.29.0 2024-04-11
kreuzwerker/docker 2.16.0 2022-01-24 3.0.2 2024-03-17
mrparkers/keycloak 3.7.0 2022-02-02 4.4.0 2024-01-08
tehcyx/kind 0.4.0 2024-02-15 0.4.0 2024-02-15

Value and/or benefit

While we might not need to have the latest versions for all the providers, we probably don't want to stay too far behind either.

Anything else?

No response

Adam-D-Lewis commented 6 months ago

It might be nice to compare release dates rather than version numbers. Maybe we make a goal/policy to use terraform providers that have been released within the last year for example.

marcelovilla commented 6 months ago

@Adam-D-Lewis I updated the issue with information about the release dates of both versions. I agree we should have some kind of policy in place. As you can see, there are some that are a couple years behind.

Also, https://github.com/gavinbunney/terraform-provider-kubectl has not seen any activity in the last two years.

viniciusdc commented 6 months ago

Also, https://github.com/gavinbunney/terraform-provider-kubectl has not seen any activity in the last two years

We should filter out where that's being used and remove if we can find a better way. This might be been used by the kind provider for authentication, though it might be good to double check if this is really needed (maybe a newer version of the kind provider does not require this anymore)