[data source] implementation google_compute_backend_bucket

[bdronneau]

Community Note

• Please vote on this issue by adding a +1 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

Terraform v0.12.20

• provider.google v2.20.2
• provider.google-beta v2.20.2

Description

Hi,
I have shared backend bucket between my loadbalancers.
Like backend service, I would like to know if there is any plan to implement google_compute_backend_bucket ?

Best

New or Affected Resource(s)

• data_google_compute_backend_bucket

[bdronneau]

Hi,

I'll propose a PR.

EDIT:

• 2.x: new data source: google_compute_backend_bucket #5699
• 3.x: features: add data_source_google_compute_backend_bucket #5700

[rileykarson]

Hey @bdronneau!

We've reserved backports for bugfixes in exceptional circumstances, generally when existing resources break due to changes in the underlying API soon after a major provider release. We use them to make sure that users aren't forced to perform a (possibly risky) migration so that their configs continue working.

I don't think that's something we'd do for a new datasource, unfortunately. If you'd like, you can run your amended 2.20.2 release including this datasource from source. Otherwise, you can use an aliased provider block to mix the 3.X datasource into the rest of your 2.X-based config.

I'm going to close out #5699, and I'll get to #5700 sometime today.

[bdronneau]

Hi @rileykarson ,

Thank for answer.

Missing alias and version does not work from my testing in terraform. I already encountered this use case when playing with module

In providers.tf:

provider "google" {
  version = "~> 3.0"
  region = "europe-west2"
}

provider "google" {
  version = "~> 2.0"
  alias  = "west"
  region = "europe-west1"
}

Output:

terraform init

Initializing the backend...

Initializing provider plugins...
- Checking for available provider plugins...

No provider "google" plugins meet the constraint "~> 2.0,~> 3.0".

The version constraint is derived from the "version" argument within the
provider "google" block in configuration. Child modules may also apply
provider version constraints. To view the provider versions requested by each
module in the current configuration, run "terraform providers".

To proceed, the version constraints for this provider must be relaxed by
either adjusting or removing the "version" argument in the provider blocks
throughout the configuration.


Error: no suitable version is available

Too bad for the backport, I'll make a less automate version of our IAC and improve it when we bump in 3.x.

[rileykarson]

Huh! I'd assumed it worked, but looks like it's intentional that it doesn't. If you're not already using google-beta you may be able to use that at a different version, since it's implemented as a different provider.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!