GuKCLPolicy
: Fix DynamoDB permissions on new KCL v3 tables
#2600
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.
In PR #2578 I failed to grant the
UpdateItem
&DeleteItem
permissions on these two new KCL v3 tables:-WorkerMetricStats
-CoordinatorState
...the permissions were correctly granted on the existing 'lease' table, so existing code based on KCL v2, worked, but as soon as the code was updated to KCL v3, errors started:
This fix correctly grants the
UpdateItem
&DeleteItem
permissions to all 3 tables.UpdateTable
is now the only permission granted solely on to the 'lease' table.For reference, the full list of IAM permissions for KCL v3 are at: