Google Cloud Storage blob store implementation #1435
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
groldan
force-pushed
the
feature/gcs_blobstore
branch
3 times, most recently
from
eeb9028 to
ddce108
Compare
Member
Author
|
|
Add support for storing tiles in Google Cloud Storage buckets, similar to the existing S3 and Azure blob stores. Tiles are organized using the standard TMS key structure. Authentication works through Application Default Credentials (the recommended approach for GCP), API keys, or anonymously for emulators. All configuration parameters support environment variable expansion. Delete operations run asynchronously and use the GCS batch API for efficiency when removing tile ranges or entire layers. This keeps the main request threads responsive during bulk operations. Includes tests using testcontainers with fake-gcs-server, comprehensive javadocs, and user documentation.
groldan
force-pushed
the
feature/gcs_blobstore
branch
from
ddce108 to
601cf88
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for storing tiles in Google Cloud Storage buckets, similar to the existing S3 and Azure blob stores. Tiles are organized using the standard TMS key structure.
Authentication works through Application Default Credentials (the recommended approach for GCP), API keys, or anonymously for emulators. All configuration parameters support environment variable expansion.
Delete operations run asynchronously and use the GCS batch API for efficiency when removing tile ranges or entire layers. This keeps the main request threads responsive during bulk operations.
Includes tests using testcontainers with fake-gcs-server, comprehensive javadocs, and user documentation.