Open
Conversation
Collaborator
|
Mentioned in slack, but current status is that the IAM role on our geoserver does not have access to the bucket included in the script update. In the meantime, I can apply the geoparquet SQL change and it would be reflected in the current bucket where these go in our account. Just lmk. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes proposed to address cross-account geoparquet write and to use a different polygon id concept (uuid), more details at https://app.asana.com/1/25496124013636/task/1213635222085401/comment/1213746614966116?focus=true
See conversation if possible, the destination bucket policy is referenced in the Asana ticket