Feat/lakeformation s3tables support #45037
Open
+122
−24
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.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
There are certain issues with LakeFormation resources and catalog IDs being on top of S3Tables catalog. In after mentioned case catalog is not AWS account ID anymore, but has one of shapes:
Issue #44888 tried to resolve problem for LF Tagging by removing validation, although it shall extend it. Issue #40724 tackles similar issue for permissions grants.
Note, that AWS API does not accept pt new catalog ID structures in "top level" requests, only in "sub sections".
Description
A new validation function, ValidCatalogID, has been introduced. It has been used in for catalog_id fields validations.
Relations
Relates #44888
Closes #40724
Output from Acceptance Testing