-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] dynamodb_table: boto3, AnsibleAwsModule, billing_mode, point_in_time_recovery and more #65
[WIP] dynamodb_table: boto3, AnsibleAwsModule, billing_mode, point_in_time_recovery and more #65
Conversation
https: //github.com/ansible/ansible/pull/45402 https: //github.com/ansible/ansible/pull/68320 https: //github.com/anryko/ansible/pull/1 Co-Authored-By: Andrej Svenke <a.shvenke@gmail.com> Co-Authored-By: sramakr <sramakr@users.noreply.github.com>
write_capacity: 10 | ||
register: result | ||
until: | ||
- result | json_query('indexes[?name==`NamedIndexV2`].read_capacity') == [10] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The json_query
filter has moved to a collection, so these will need to be community.general.json_query
.
dynamodb_table: | ||
name: "{{ table_name }}" | ||
hash_key_name: myhashkey | ||
indexes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AWS permits only one index to be created in a single action, this task is throwing an unhandled ClientError. The code should reflect and enforce the service limits.
botocore.errorfactory.LimitExceededException: An error occurred (LimitExceededException) when calling the UpdateTable operation: Subscriber limit exceeded: Only 1 online index can be created or deleted simultaneously per table
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html#limits-secondary-indexes
I haven't done a proper review of the code, but there doesn't seem to be much exception handling. We generally like to catch ClientError
and BotoCoreError
.
Hi guys, |
Hey I completely forgot to pick this back up again, I'll try and get it all up-to-date again and address the feedback on the PR |
@marknet15 this PR contains the following merge commits: Please rebase your branch to remove these commits. |
I've started working on a simple boto3 migration (#726) while that won't add the extra features it should be easier to review and much simpler to add features to an existing framework. |
@tremble Ah I had completely forgotten about this PR, I'll close it then I'll create a fresh PR with the extra functionality after your boto -> boto3 migration |
dynamodb_table - boto3 migration SUMMARY Existing boto3 migration (#65) seems to have been mangled by the migration to collections and has bit-rotted. Start from scratch and don't add new features. ISSUE TYPE Feature Pull Request COMPONENT NAME dynamodb_table ADDITIONAL INFORMATION Reviewed-by: Mark Woolley <mw@marknet15.com> Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
SUMMARY
This is a fresh PR to transfer over the original PR from the ansible repo to the new community.aws repo as requested to meet new requirements.
Original PR's
ansible/ansible#45402
ansible/ansible#68320
anryko/ansible#1
I'm providing the fixes listed below for the changes proposed in ansible/ansible#68320 that are now stale that is in turn based on the below:
Fixes:
ProvisionedThroughput
params being set incorrectly on GSI's when billing isPAY_PER_REQUEST
.key_type_mapping
.serialized_index_attribute_definitions
for both the hash and the range key on a GSI. (range key definition was being overwritten).Fixes #45402
Fixes #56923
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION