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

storage: Support custom endpoints for SignURLs #13068

Open
BrennaEpp opened this issue Nov 8, 2023 · 1 comment · May be fixed by #14179
Open

storage: Support custom endpoints for SignURLs #13068

BrennaEpp opened this issue Nov 8, 2023 · 1 comment · May be fixed by #14179
Assignees
Labels
api: storage Issues related to the Cloud Storage API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@BrennaEpp
Copy link

BrennaEpp commented Nov 8, 2023

When a custom endpoint is set on the client, Sign URLs and Post Policies should automatically use that domain.

Optional: allow users to set a custom hostname for Sign URL and Post policy methods.

See the following for more information and fill out language section: go/signurl-custom-endpoint-gcs
Please add a comment or ping me if you have any questions.

@BrennaEpp BrennaEpp added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Nov 8, 2023
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Nov 8, 2023
@coryan coryan removed their assignment Mar 7, 2024
@coryan
Copy link
Member

coryan commented Mar 7, 2024

I won't be working on this for a while. When I start working on this problem I will assign the bug to myself.

@bajajneha27 bajajneha27 self-assigned this Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants