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

Add capability to GCS backend to allow use of a Private Service Connect endpoint for Google Storage API #28856

Closed
nathanzanon opened this issue Jun 1, 2021 · 1 comment · Fixed by #31967

Comments

@nathanzanon
Copy link

Current Terraform Version

Terraform v0.15.4
on darwin_amd64

Use-cases

To use the Google Cloud Storage (GCS) backend through a Private Service Connect endpoint, which can be used to provide a custom endpoint for the Storage API, e.g. storage-xyz.p.googleapis.com.

Using a custom endpoint with GCS should be able to be configured in the backend block, or through an OS environment variable.

Attempted Solutions

None

Proposal

The Private Service Connect endpoint documentation provides the following info:

Go: You can configure WithEndpoint in the Client options package in the api package.

To allow specifying custom endpoints for the GCS API, e.g. storage-xyz.p.googleapis.com.

Then from a usage perspective I believe this could follow a similar implementation method to the S3 backend config that can be specified through endpoint.

References

None

@nathanzanon nathanzanon added enhancement new new issue not yet triaged labels Jun 1, 2021
@jbardin jbardin added backend/gcs and removed new new issue not yet triaged labels Jun 2, 2021
@SarahFrench SarahFrench self-assigned this Oct 7, 2022
@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants