Add -s option to enforce source bucket name #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request introduces a new
-sCLI option that allows specifying a bucket name directly instead of extracting it from the requested paths.My use case
I'm hosting a private website with a private bucket protected by Identity-Aware Proxy (IAP).
flowchart LR http(http)---LB-with-IAP subgraph LB-with-IAP direction TB A[Identity-Aware Proxy].->B[Application Load Balancer] end LB-with-IAP---cloud-run[Cloud Run - gcsproxy] cloud-run---bucket[(Private Bucket)]The path rewriting feature provided by the load balancer can be used to pass the bucket name to gcsproxy.
However, this setup creates an issue when combined with IAP. When IAP is enabled, it processes requests after the path has been rewritten. As a result, the redirect URL after completing the authentication flow will include the rewritten path prefix, which is unintended. Using the new
-soption instead of path rewriting resolves this issue.