Add a class level store in models/VPCPeeringConnectionBackend of ec2
for saving vpc peering connection.
Any instance can correctly save VPC peering connection info
on both region when it create vpc peering connection.
Update vpc_peering_connections in ec2/responses to meet new version:
DESCRIBE_VPC_PEERING_CONNECTIONS_RESPONSE,
ACCEPT_VPC_PEERING_CONNECTION_RESPONSE,
Previous code only create one region VPC peering connection but
doesn't create the other region VPC peering connection
when create cross region VPC peering connection.
Tested in real AWS environment at first
and create unit test case according to real AWS environment response.
Add 5 test cases
VPC cross region delete case
VPC cross region accept case
VPC cross region accept wrong region case
VPC cross region reject case
VPC cross region reject wrong region case
Related: #1842, #1830
adding support for organizations service control policies
* [Resolves#2196] - endpoints for querying organizations SC policies
I have added the following mock endpoints to the Organizations service:
- create_policy
- list_policies
- describe_policy
- attach_policy
- list_policies_for_target
- list_targets_for_policy
* add proper retentionInDays to describe_log_groups response and add support for delete_retention_policy() and put_retention_policy() to log groups
* fix for inline comment formatting
* include check for retentionInDays to verify no retention by default in test_log_group_create
* initial work
- adding put_secret_value and list_secret_versions
* Added support for versions in all functions except rotate_secret
* more work
- refactor rotate_secret method
- now, adds a new version of the secret and points default version id to it
- updated implementation coverage readme
- element in list check to fix unit test
- fixed linting errors
- added tests, fixed exception, failing tests still
- secrets_manager/test_server fails when running whole suite,
but not when running that individual test file
* fixed failing test_get_secret_value
* Removed test.py. Fixed condition statement.
* fixed default stages + adding AWSPREVIOUS
* remove old AWSPREVIOUS stages
* Adding support for specifying a PermissionsBoundary ARN in calls to iam.create_role
Closes#2181
* Correcting whitespace error
* Adding support for Role PermissionsBoundary to be returned from
calls to list_roles
* Raise ClientError when a bad permissions boundary ARN is supplied
* Updated the deprecated decorator to allow the "SkipFinalClusterSnapshot" option that aws supports.
* FIxed logical mistake on the delete_cluster
* Removed an unused exception I put in
* Added KMS.generate_data_key and KMS.generate_date_key_without_plaintext
Increase test coverage to cover Key not found
* Added test for kms.put_key_policy key not found
When creating a new IAM policy version with create_policy_version,
we cannot use the length of the versions list to calculate VersionId.
Keep track of the next version id to use as a non-decreasing counter.
Fixes#2157
