capo-redshift-serverless 0.3.0__tar.gz → 0.4.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {capo_redshift_serverless-0.3.0/src/capo_redshift_serverless.egg-info → capo_redshift_serverless-0.4.0}/PKG-INFO +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/pyproject.toml +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/recovery_point_resource.py +4 -4
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/reservation_resource.py +4 -4
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/scheduled_action_resource.py +14 -14
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/snapshot_resource.py +6 -6
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/workgroup_resource.py +8 -8
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_services/async_redshift_serverless.py +21 -21
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_services/redshift_serverless.py +21 -21
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/config_parameter.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/convert_recovery_point_to_snapshot_request.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_reservation_request.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_scheduled_action_request.py +3 -3
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_snapshot_request.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_snapshot_schedule_action_parameters.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_workgroup_request.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_credentials_request.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/namespace.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/put_resource_policy_request.py +1 -1
- capo_redshift_serverless-0.4.0/src/capo_redshift_serverless/types/s3_table_name.py +6 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/scheduled_action_response.py +2 -2
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_scheduled_action_request.py +2 -2
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_workgroup_request.py +1 -1
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/workgroup.py +3 -3
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0/src/capo_redshift_serverless.egg-info}/PKG-INFO +1 -1
- capo_redshift_serverless-0.3.0/src/capo_redshift_serverless/types/s3_table_name.py +0 -6
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/LICENSE +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/README.md +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/setup.cfg +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/__init__.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_async.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_auth/_identity.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_auth/_providers.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_auth/_signers.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_auth/_sigv4.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_auth/_zapros_handler.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_body.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_iter.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/convert_recovery_point_to_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_custom_domain_association.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_endpoint_access.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_namespace.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_reservation.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_scheduled_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_snapshot_copy_configuration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_usage_limit.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/create_workgroup.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_custom_domain_association.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_endpoint_access.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_namespace.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_resource_policy.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_scheduled_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_snapshot_copy_configuration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_usage_limit.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/delete_workgroup.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_credentials.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_custom_domain_association.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_endpoint_access.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_identity_center_auth_token.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_namespace.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_recovery_point.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_reservation.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_reservation_offering.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_resource_policy.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_scheduled_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_table_restore_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_track.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_usage_limit.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/get_workgroup.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_custom_domain_associations.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_endpoint_access.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_managed_workgroups.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_namespaces.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_recovery_points.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_reservation_offerings.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_reservations.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_scheduled_actions.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_snapshot_copy_configurations.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_snapshots.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_table_restore_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_tags_for_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_tracks.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_usage_limits.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/list_workgroups.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/put_resource_policy.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/restore_from_recovery_point.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/restore_from_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/restore_table_from_recovery_point.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/restore_table_from_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/tag_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/untag_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_custom_domain_association.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_endpoint_access.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_lakehouse_configuration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_namespace.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_scheduled_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_snapshot_copy_configuration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_usage_limit.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_operations/redshift_serverless/update_workgroup.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_pagination.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_protocol/__init__.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_protocol/errors.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_protocol/eventstream.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_protocol/serialize.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_protocol/xml.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/cross_vpc_endpoint_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/managed_workgroup_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/namespace_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_resources/redshift_serverless/usage_limit_resource.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_rule_engine/__init__.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_rule_engine/_aws_partition.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_rule_engine/_endpoint_rule_set.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_rule_engine/_endpoint_runtime.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_services/_aws_config.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/_services/_pipeline.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/__init__.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/_base.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/access_denied_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/conflict_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/dry_run_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/insufficient_capacity_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/internal_server_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/invalid_pagination_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/ipv6_cidr_block_not_found_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/resource_not_found_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/service_quota_exceeded_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/throttling_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/too_many_tags_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/errors/validation_exception.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/py.typed +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/_prelude/blob.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/_prelude/timestamp.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/account_id_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/amazon_resource_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/association.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/association_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/capacity.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/catalog_name_string.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/charge.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/config_parameter_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/convert_recovery_point_to_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_custom_domain_association_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_custom_domain_association_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_endpoint_access_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_endpoint_access_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_namespace_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_namespace_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_reservation_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_scheduled_action_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_snapshot_copy_configuration_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_snapshot_copy_configuration_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_usage_limit_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_usage_limit_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/create_workgroup_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/currency_code.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/custom_domain_certificate_arn_string.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/custom_domain_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/db_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/db_password.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/db_user.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_custom_domain_association_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_custom_domain_association_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_endpoint_access_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_endpoint_access_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_namespace_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_namespace_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_resource_policy_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_resource_policy_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_scheduled_action_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_scheduled_action_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_snapshot_copy_configuration_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_snapshot_copy_configuration_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_snapshot_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_usage_limit_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_usage_limit_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_workgroup_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/delete_workgroup_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/duration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/endpoint.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/endpoint_access.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/endpoint_access_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_credentials_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_custom_domain_association_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_custom_domain_association_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_endpoint_access_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_endpoint_access_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_identity_center_auth_token_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_identity_center_auth_token_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_namespace_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_namespace_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_recovery_point_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_recovery_point_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_reservation_offering_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_reservation_offering_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_reservation_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_reservation_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_resource_policy_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_resource_policy_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_scheduled_action_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_scheduled_action_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_snapshot_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_table_restore_status_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_table_restore_status_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_track_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_track_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_usage_limit_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_usage_limit_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_workgroup_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/get_workgroup_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/iam_role_arn.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/iam_role_arn_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/ip_address_type.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/kms_key_id.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/lakehouse_idc_registration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/lakehouse_registration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_custom_domain_associations_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_custom_domain_associations_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_endpoint_access_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_endpoint_access_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_managed_workgroups_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_managed_workgroups_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_namespaces_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_namespaces_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_recovery_points_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_recovery_points_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_reservation_offerings_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_reservation_offerings_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_reservations_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_reservations_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_scheduled_actions_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_scheduled_actions_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_snapshot_copy_configurations_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_snapshot_copy_configurations_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_snapshots_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_snapshots_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_table_restore_status_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_table_restore_status_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_tags_for_resource_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_tags_for_resource_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_tracks_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_tracks_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_usage_limits_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_usage_limits_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_workgroups_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/list_workgroups_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/log_destination_type.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/log_export.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/log_export_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/managed_workgroup_list_item.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/managed_workgroup_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/managed_workgroup_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/managed_workgroups.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/namespace_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/namespace_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/namespace_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/network_interface.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/network_interface_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/next_invocations_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/offering_id.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/offering_type.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/owner_account.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/pagination_token.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/parameter_key.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/parameter_value.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/performance_target.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/performance_target_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/put_resource_policy_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/recovery_point.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/recovery_point_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/redshift_idc_application_arn.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/reservation.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/reservation_arn.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/reservation_id.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/reservation_offering.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/reservation_offerings_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/reservations_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/resource_policy.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_from_recovery_point_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_from_recovery_point_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_from_snapshot_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_from_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_table_from_recovery_point_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_table_from_recovery_point_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_table_from_snapshot_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/restore_table_from_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/s3_table_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/s3_table_granularity.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/s3_table_last_ingestion_time_map.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/s3_table_name_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/s3_table_publish_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/schedule.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/scheduled_action_association.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/scheduled_action_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/scheduled_actions_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/security_group_id.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/security_group_id_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/serverless_track.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/snapshot.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/snapshot_copy_configuration.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/snapshot_copy_configurations.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/snapshot_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/snapshot_name_prefix.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/snapshot_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/source_arn.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/state.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/subnet_id.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/subnet_id_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/table_restore_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/table_restore_status_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag_key.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag_key_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag_resource_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag_resource_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/tag_value.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/target_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/track_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/track_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/untag_resource_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/untag_resource_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_custom_domain_association_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_custom_domain_association_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_endpoint_access_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_endpoint_access_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_lakehouse_configuration_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_lakehouse_configuration_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_namespace_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_namespace_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_scheduled_action_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_snapshot_copy_configuration_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_snapshot_copy_configuration_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_snapshot_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_snapshot_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_target.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_targets_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_usage_limit_request.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_usage_limit_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/update_workgroup_response.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/usage_limit.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/usage_limit_breach_action.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/usage_limit_period.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/usage_limit_usage_type.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/usage_limits.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_endpoint.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_endpoint_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_ids.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_security_group_id.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_security_group_id_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_security_group_membership.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/vpc_security_group_membership_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/workgroup_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/workgroup_name.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/workgroup_name_list.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless/types/workgroup_status.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless.egg-info/SOURCES.txt +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless.egg-info/dependency_links.txt +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless.egg-info/requires.txt +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/src/capo_redshift_serverless.egg-info/top_level.txt +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/tests/test_body.py +0 -0
- {capo_redshift_serverless-0.3.0 → capo_redshift_serverless-0.4.0}/tests/test_sigv4.py +0 -0
|
@@ -50,13 +50,13 @@ class RecoveryPointResource:
|
|
|
50
50
|
retention_period: Optional[int] = None,
|
|
51
51
|
tags: Optional["capo_redshift_serverless.types.tag_list.TagList"] = None,
|
|
52
52
|
) -> "capo_redshift_serverless.types.convert_recovery_point_to_snapshot_response.ConvertRecoveryPointToSnapshotResponse":
|
|
53
|
-
|
|
53
|
+
"""<p>Converts a recovery point to a snapshot. For more information about recovery points and snapshots, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-snapshots-recovery-points.html">Working with snapshots and recovery points</a>.</p>
|
|
54
54
|
|
|
55
55
|
Args:
|
|
56
56
|
recovery_point_id: <p>The unique identifier of the recovery point.</p>
|
|
57
57
|
snapshot_name: <p>The name of the snapshot.</p>
|
|
58
58
|
retention_period: <p>How long to retain the snapshot.</p>
|
|
59
|
-
tags: <p>An array of <a href
|
|
59
|
+
tags: <p>An array of <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_Tag.html">Tag objects</a> to associate with the created snapshot.</p>
|
|
60
60
|
|
|
61
61
|
Raises:
|
|
62
62
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -361,13 +361,13 @@ class AsyncRecoveryPointResource:
|
|
|
361
361
|
retention_period: Optional[int] = None,
|
|
362
362
|
tags: Optional["capo_redshift_serverless.types.tag_list.TagList"] = None,
|
|
363
363
|
) -> "capo_redshift_serverless.types.convert_recovery_point_to_snapshot_response.ConvertRecoveryPointToSnapshotResponse":
|
|
364
|
-
|
|
364
|
+
"""<p>Converts a recovery point to a snapshot. For more information about recovery points and snapshots, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-snapshots-recovery-points.html">Working with snapshots and recovery points</a>.</p>
|
|
365
365
|
|
|
366
366
|
Args:
|
|
367
367
|
recovery_point_id: <p>The unique identifier of the recovery point.</p>
|
|
368
368
|
snapshot_name: <p>The name of the snapshot.</p>
|
|
369
369
|
retention_period: <p>How long to retain the snapshot.</p>
|
|
370
|
-
tags: <p>An array of <a href
|
|
370
|
+
tags: <p>An array of <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_Tag.html">Tag objects</a> to associate with the created snapshot.</p>
|
|
371
371
|
|
|
372
372
|
Raises:
|
|
373
373
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -51,12 +51,12 @@ class ReservationResource:
|
|
|
51
51
|
config_overrides: Optional[RedshiftServerlessClientConfig] = None,
|
|
52
52
|
client_token: Optional[str] = None,
|
|
53
53
|
) -> "capo_redshift_serverless.types.create_reservation_response.CreateReservationResponse":
|
|
54
|
-
|
|
54
|
+
"""<p>Creates an Amazon Redshift Serverless reservation, which gives you the option to commit to a specified number of Redshift Processing Units (RPUs) for a year at a discount from Serverless on-demand (OD) rates.</p>
|
|
55
55
|
|
|
56
56
|
Args:
|
|
57
57
|
capacity: <p>The number of Redshift Processing Units (RPUs) to reserve.</p>
|
|
58
58
|
offering_id: <p>The ID of the offering associated with the reservation. The offering determines the payment schedule for the reservation.</p>
|
|
59
|
-
client_token: <p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. This token must be a valid UUIDv4 value. For more information about idempotency, see <a href
|
|
59
|
+
client_token: <p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. This token must be a valid UUIDv4 value. For more information about idempotency, see <a href="https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/"> Making retries safe with idempotent APIs </a>.</p>
|
|
60
60
|
|
|
61
61
|
Raises:
|
|
62
62
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -309,12 +309,12 @@ class AsyncReservationResource:
|
|
|
309
309
|
config_overrides: Optional[AsyncRedshiftServerlessClientConfig] = None,
|
|
310
310
|
client_token: Optional[str] = None,
|
|
311
311
|
) -> "capo_redshift_serverless.types.create_reservation_response.CreateReservationResponse":
|
|
312
|
-
|
|
312
|
+
"""<p>Creates an Amazon Redshift Serverless reservation, which gives you the option to commit to a specified number of Redshift Processing Units (RPUs) for a year at a discount from Serverless on-demand (OD) rates.</p>
|
|
313
313
|
|
|
314
314
|
Args:
|
|
315
315
|
capacity: <p>The number of Redshift Processing Units (RPUs) to reserve.</p>
|
|
316
316
|
offering_id: <p>The ID of the offering associated with the reservation. The offering determines the payment schedule for the reservation.</p>
|
|
317
|
-
client_token: <p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. This token must be a valid UUIDv4 value. For more information about idempotency, see <a href
|
|
317
|
+
client_token: <p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. This token must be a valid UUIDv4 value. For more information about idempotency, see <a href="https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/"> Making retries safe with idempotent APIs </a>.</p>
|
|
318
318
|
|
|
319
319
|
Raises:
|
|
320
320
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -58,14 +58,14 @@ class ScheduledActionResource:
|
|
|
58
58
|
start_time: Optional[datetime.datetime] = None,
|
|
59
59
|
end_time: Optional[datetime.datetime] = None,
|
|
60
60
|
) -> "capo_redshift_serverless.types.create_scheduled_action_response.CreateScheduledActionResponse":
|
|
61
|
-
|
|
61
|
+
"""<p>Creates a scheduled action. A scheduled action contains a schedule and an Amazon Redshift API action. For example, you can create a schedule of when to run the <code>CreateSnapshot</code> API operation.</p>
|
|
62
62
|
|
|
63
63
|
Args:
|
|
64
64
|
scheduled_action_name: <p>The name of the scheduled action.</p>
|
|
65
|
-
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code
|
|
66
|
-
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots. (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href
|
|
65
|
+
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code>"(0 10 ? * MON *)"</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions">Cron Expressions</a> in the <i>Amazon CloudWatch Events User Guide</i>.</p> </li> </ul>
|
|
66
|
+
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots. (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html">Using Identity-Based Policies for Amazon Redshift</a> in the Amazon Redshift Management Guide</p>
|
|
67
67
|
namespace_name: <p>The name of the namespace for which to create a scheduled action.</p>
|
|
68
|
-
enabled: <p>Indicates whether the schedule is enabled. If false, the scheduled action does not trigger. For more information about <code>state</code> of the scheduled action, see <a href
|
|
68
|
+
enabled: <p>Indicates whether the schedule is enabled. If false, the scheduled action does not trigger. For more information about <code>state</code> of the scheduled action, see <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_ScheduledAction.html">ScheduledAction</a>.</p>
|
|
69
69
|
scheduled_action_description: <p>The description of the scheduled action.</p>
|
|
70
70
|
start_time: <p>The start time in UTC when the schedule is active. Before this time, the scheduled action does not trigger.</p>
|
|
71
71
|
end_time: <p>The end time in UTC when the schedule is no longer active. After this time, the scheduled action does not trigger.</p>
|
|
@@ -282,12 +282,12 @@ class ScheduledActionResource:
|
|
|
282
282
|
start_time: Optional[datetime.datetime] = None,
|
|
283
283
|
end_time: Optional[datetime.datetime] = None,
|
|
284
284
|
) -> "capo_redshift_serverless.types.update_scheduled_action_response.UpdateScheduledActionResponse":
|
|
285
|
-
|
|
285
|
+
"""<p>Updates a scheduled action.</p>
|
|
286
286
|
|
|
287
287
|
Args:
|
|
288
288
|
scheduled_action_name: <p>The name of the scheduled action to update to.</p>
|
|
289
|
-
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code
|
|
290
|
-
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href
|
|
289
|
+
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code>"(0 10 ? * MON *)"</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions">Cron Expressions</a> in the <i>Amazon CloudWatch Events User Guide</i>.</p> </li> </ul>
|
|
290
|
+
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html">Using Identity-Based Policies for Amazon Redshift</a> in the Amazon Redshift Management Guide</p>
|
|
291
291
|
enabled: <p>Specifies whether to enable the scheduled action.</p>
|
|
292
292
|
scheduled_action_description: <p>The descripion of the scheduled action to update to.</p>
|
|
293
293
|
start_time: <p>The start time in UTC of the scheduled action to update to.</p>
|
|
@@ -361,14 +361,14 @@ class AsyncScheduledActionResource:
|
|
|
361
361
|
start_time: Optional[datetime.datetime] = None,
|
|
362
362
|
end_time: Optional[datetime.datetime] = None,
|
|
363
363
|
) -> "capo_redshift_serverless.types.create_scheduled_action_response.CreateScheduledActionResponse":
|
|
364
|
-
|
|
364
|
+
"""<p>Creates a scheduled action. A scheduled action contains a schedule and an Amazon Redshift API action. For example, you can create a schedule of when to run the <code>CreateSnapshot</code> API operation.</p>
|
|
365
365
|
|
|
366
366
|
Args:
|
|
367
367
|
scheduled_action_name: <p>The name of the scheduled action.</p>
|
|
368
|
-
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code
|
|
369
|
-
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots. (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href
|
|
368
|
+
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code>"(0 10 ? * MON *)"</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions">Cron Expressions</a> in the <i>Amazon CloudWatch Events User Guide</i>.</p> </li> </ul>
|
|
369
|
+
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots. (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html">Using Identity-Based Policies for Amazon Redshift</a> in the Amazon Redshift Management Guide</p>
|
|
370
370
|
namespace_name: <p>The name of the namespace for which to create a scheduled action.</p>
|
|
371
|
-
enabled: <p>Indicates whether the schedule is enabled. If false, the scheduled action does not trigger. For more information about <code>state</code> of the scheduled action, see <a href
|
|
371
|
+
enabled: <p>Indicates whether the schedule is enabled. If false, the scheduled action does not trigger. For more information about <code>state</code> of the scheduled action, see <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_ScheduledAction.html">ScheduledAction</a>.</p>
|
|
372
372
|
scheduled_action_description: <p>The description of the scheduled action.</p>
|
|
373
373
|
start_time: <p>The start time in UTC when the schedule is active. Before this time, the scheduled action does not trigger.</p>
|
|
374
374
|
end_time: <p>The end time in UTC when the schedule is no longer active. After this time, the scheduled action does not trigger.</p>
|
|
@@ -589,12 +589,12 @@ class AsyncScheduledActionResource:
|
|
|
589
589
|
start_time: Optional[datetime.datetime] = None,
|
|
590
590
|
end_time: Optional[datetime.datetime] = None,
|
|
591
591
|
) -> "capo_redshift_serverless.types.update_scheduled_action_response.UpdateScheduledActionResponse":
|
|
592
|
-
|
|
592
|
+
"""<p>Updates a scheduled action.</p>
|
|
593
593
|
|
|
594
594
|
Args:
|
|
595
595
|
scheduled_action_name: <p>The name of the scheduled action to update to.</p>
|
|
596
|
-
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code
|
|
597
|
-
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href
|
|
596
|
+
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code>"(0 10 ? * MON *)"</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions">Cron Expressions</a> in the <i>Amazon CloudWatch Events User Guide</i>.</p> </li> </ul>
|
|
597
|
+
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html">Using Identity-Based Policies for Amazon Redshift</a> in the Amazon Redshift Management Guide</p>
|
|
598
598
|
enabled: <p>Specifies whether to enable the scheduled action.</p>
|
|
599
599
|
scheduled_action_description: <p>The descripion of the scheduled action to update to.</p>
|
|
600
600
|
start_time: <p>The start time in UTC of the scheduled action to update to.</p>
|
|
@@ -72,13 +72,13 @@ class SnapshotResource:
|
|
|
72
72
|
) -> (
|
|
73
73
|
"capo_redshift_serverless.types.create_snapshot_response.CreateSnapshotResponse"
|
|
74
74
|
):
|
|
75
|
-
|
|
75
|
+
"""<p>Creates a snapshot of all databases in a namespace. For more information about snapshots, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-snapshots-recovery-points.html"> Working with snapshots and recovery points</a>.</p>
|
|
76
76
|
|
|
77
77
|
Args:
|
|
78
78
|
namespace_name: <p>The namespace to create a snapshot for.</p>
|
|
79
79
|
snapshot_name: <p>The name of the snapshot.</p>
|
|
80
80
|
retention_period: <p>How long to retain the created snapshot.</p>
|
|
81
|
-
tags: <p>An array of <a href
|
|
81
|
+
tags: <p>An array of <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_Tag.html">Tag objects</a> to associate with the snapshot.</p>
|
|
82
82
|
|
|
83
83
|
Raises:
|
|
84
84
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -655,7 +655,7 @@ class SnapshotResource:
|
|
|
655
655
|
target_schema_name: Optional[str] = None,
|
|
656
656
|
activate_case_sensitive_identifier: Optional[bool] = None,
|
|
657
657
|
) -> "capo_redshift_serverless.types.restore_table_from_snapshot_response.RestoreTableFromSnapshotResponse":
|
|
658
|
-
|
|
658
|
+
"""<p>Restores a table from a snapshot to your Amazon Redshift Serverless instance. You can't use this operation to restore tables with <a href="https://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html#t_Sorting_data-interleaved">interleaved sort keys</a>.</p>
|
|
659
659
|
|
|
660
660
|
Args:
|
|
661
661
|
namespace_name: <p>The namespace of the snapshot to restore from.</p>
|
|
@@ -838,13 +838,13 @@ class AsyncSnapshotResource:
|
|
|
838
838
|
) -> (
|
|
839
839
|
"capo_redshift_serverless.types.create_snapshot_response.CreateSnapshotResponse"
|
|
840
840
|
):
|
|
841
|
-
|
|
841
|
+
"""<p>Creates a snapshot of all databases in a namespace. For more information about snapshots, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-snapshots-recovery-points.html"> Working with snapshots and recovery points</a>.</p>
|
|
842
842
|
|
|
843
843
|
Args:
|
|
844
844
|
namespace_name: <p>The namespace to create a snapshot for.</p>
|
|
845
845
|
snapshot_name: <p>The name of the snapshot.</p>
|
|
846
846
|
retention_period: <p>How long to retain the created snapshot.</p>
|
|
847
|
-
tags: <p>An array of <a href
|
|
847
|
+
tags: <p>An array of <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_Tag.html">Tag objects</a> to associate with the snapshot.</p>
|
|
848
848
|
|
|
849
849
|
Raises:
|
|
850
850
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -1431,7 +1431,7 @@ class AsyncSnapshotResource:
|
|
|
1431
1431
|
target_schema_name: Optional[str] = None,
|
|
1432
1432
|
activate_case_sensitive_identifier: Optional[bool] = None,
|
|
1433
1433
|
) -> "capo_redshift_serverless.types.restore_table_from_snapshot_response.RestoreTableFromSnapshotResponse":
|
|
1434
|
-
|
|
1434
|
+
"""<p>Restores a table from a snapshot to your Amazon Redshift Serverless instance. You can't use this operation to restore tables with <a href="https://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html#t_Sorting_data-interleaved">interleaved sort keys</a>.</p>
|
|
1435
1435
|
|
|
1436
1436
|
Args:
|
|
1437
1437
|
namespace_name: <p>The namespace of the snapshot to restore from.</p>
|
|
@@ -79,14 +79,14 @@ class WorkgroupResource:
|
|
|
79
79
|
] = None,
|
|
80
80
|
extra_compute_for_automatic_optimization: Optional[bool] = None,
|
|
81
81
|
) -> "capo_redshift_serverless.types.create_workgroup_response.CreateWorkgroupResponse":
|
|
82
|
-
|
|
82
|
+
"""<p>Creates an workgroup in Amazon Redshift Serverless.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a workgroup is in an account with VPC BPA turned on, the following capabilities are blocked: </p> <ul> <li> <p>Creating a public access workgroup</p> </li> <li> <p>Modifying a private workgroup to public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the workgroup when the workgroup is public</p> </li> </ul> <p>For more information about VPC BPA, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>
|
|
83
83
|
|
|
84
84
|
Args:
|
|
85
85
|
workgroup_name: <p>The name of the created workgroup.</p>
|
|
86
86
|
namespace_name: <p>The name of the namespace to associate with the workgroup.</p>
|
|
87
87
|
base_capacity: <p>The base data warehouse capacity of the workgroup in Redshift Processing Units (RPUs).</p>
|
|
88
88
|
enhanced_vpc_routing: <p>The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC instead of over the internet.</p>
|
|
89
|
-
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href
|
|
89
|
+
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href="https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html#cm-c-wlm-query-monitoring-metrics-serverless"> Query monitoring metrics for Amazon Redshift Serverless</a>.</p>
|
|
90
90
|
security_group_ids: <p>An array of security group IDs to associate with the workgroup.</p>
|
|
91
91
|
subnet_ids: <p>An array of VPC subnet IDs to associate with the workgroup.</p>
|
|
92
92
|
publicly_accessible: <p>A value that specifies whether the workgroup can be accessed from a public network.</p>
|
|
@@ -240,13 +240,13 @@ class WorkgroupResource:
|
|
|
240
240
|
] = None,
|
|
241
241
|
extra_compute_for_automatic_optimization: Optional[bool] = None,
|
|
242
242
|
) -> "capo_redshift_serverless.types.update_workgroup_response.UpdateWorkgroupResponse":
|
|
243
|
-
|
|
243
|
+
"""<p>Updates a workgroup with the specified configuration settings. You can't update multiple parameters in one request. For example, you can update <code>baseCapacity</code> or <code>port</code> in a single request, but you can't update both in the same request.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a workgroup is in an account with VPC BPA turned on, the following capabilities are blocked: </p> <ul> <li> <p>Creating a public access workgroup</p> </li> <li> <p>Modifying a private workgroup to public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the workgroup when the workgroup is public</p> </li> </ul> <p>For more information about VPC BPA, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>
|
|
244
244
|
|
|
245
245
|
Args:
|
|
246
246
|
workgroup_name: <p>The name of the workgroup to update. You can't update the name of a workgroup once it is created.</p>
|
|
247
247
|
base_capacity: <p>The new base data warehouse capacity in Redshift Processing Units (RPUs).</p>
|
|
248
248
|
enhanced_vpc_routing: <p>The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC.</p>
|
|
249
|
-
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href
|
|
249
|
+
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href="https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html#cm-c-wlm-query-monitoring-metrics-serverless"> Query monitoring metrics for Amazon Redshift Serverless</a>.</p>
|
|
250
250
|
publicly_accessible: <p>A value that specifies whether the workgroup can be accessible from a public network.</p>
|
|
251
251
|
subnet_ids: <p>An array of VPC subnet IDs to associate with the workgroup.</p>
|
|
252
252
|
security_group_ids: <p>An array of security group IDs to associate with the workgroup.</p>
|
|
@@ -459,14 +459,14 @@ class AsyncWorkgroupResource:
|
|
|
459
459
|
] = None,
|
|
460
460
|
extra_compute_for_automatic_optimization: Optional[bool] = None,
|
|
461
461
|
) -> "capo_redshift_serverless.types.create_workgroup_response.CreateWorkgroupResponse":
|
|
462
|
-
|
|
462
|
+
"""<p>Creates an workgroup in Amazon Redshift Serverless.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a workgroup is in an account with VPC BPA turned on, the following capabilities are blocked: </p> <ul> <li> <p>Creating a public access workgroup</p> </li> <li> <p>Modifying a private workgroup to public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the workgroup when the workgroup is public</p> </li> </ul> <p>For more information about VPC BPA, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>
|
|
463
463
|
|
|
464
464
|
Args:
|
|
465
465
|
workgroup_name: <p>The name of the created workgroup.</p>
|
|
466
466
|
namespace_name: <p>The name of the namespace to associate with the workgroup.</p>
|
|
467
467
|
base_capacity: <p>The base data warehouse capacity of the workgroup in Redshift Processing Units (RPUs).</p>
|
|
468
468
|
enhanced_vpc_routing: <p>The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC instead of over the internet.</p>
|
|
469
|
-
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href
|
|
469
|
+
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href="https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html#cm-c-wlm-query-monitoring-metrics-serverless"> Query monitoring metrics for Amazon Redshift Serverless</a>.</p>
|
|
470
470
|
security_group_ids: <p>An array of security group IDs to associate with the workgroup.</p>
|
|
471
471
|
subnet_ids: <p>An array of VPC subnet IDs to associate with the workgroup.</p>
|
|
472
472
|
publicly_accessible: <p>A value that specifies whether the workgroup can be accessed from a public network.</p>
|
|
@@ -622,13 +622,13 @@ class AsyncWorkgroupResource:
|
|
|
622
622
|
] = None,
|
|
623
623
|
extra_compute_for_automatic_optimization: Optional[bool] = None,
|
|
624
624
|
) -> "capo_redshift_serverless.types.update_workgroup_response.UpdateWorkgroupResponse":
|
|
625
|
-
|
|
625
|
+
"""<p>Updates a workgroup with the specified configuration settings. You can't update multiple parameters in one request. For example, you can update <code>baseCapacity</code> or <code>port</code> in a single request, but you can't update both in the same request.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a workgroup is in an account with VPC BPA turned on, the following capabilities are blocked: </p> <ul> <li> <p>Creating a public access workgroup</p> </li> <li> <p>Modifying a private workgroup to public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the workgroup when the workgroup is public</p> </li> </ul> <p>For more information about VPC BPA, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>
|
|
626
626
|
|
|
627
627
|
Args:
|
|
628
628
|
workgroup_name: <p>The name of the workgroup to update. You can't update the name of a workgroup once it is created.</p>
|
|
629
629
|
base_capacity: <p>The new base data warehouse capacity in Redshift Processing Units (RPUs).</p>
|
|
630
630
|
enhanced_vpc_routing: <p>The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC.</p>
|
|
631
|
-
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href
|
|
631
|
+
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href="https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html#cm-c-wlm-query-monitoring-metrics-serverless"> Query monitoring metrics for Amazon Redshift Serverless</a>.</p>
|
|
632
632
|
publicly_accessible: <p>A value that specifies whether the workgroup can be accessible from a public network.</p>
|
|
633
633
|
subnet_ids: <p>An array of VPC subnet IDs to associate with the workgroup.</p>
|
|
634
634
|
security_group_ids: <p>An array of security group IDs to associate with the workgroup.</p>
|
|
@@ -518,10 +518,10 @@ class AsyncRedshiftServerlessClient:
|
|
|
518
518
|
) -> (
|
|
519
519
|
"capo_redshift_serverless.types.get_credentials_response.GetCredentialsResponse"
|
|
520
520
|
):
|
|
521
|
-
|
|
521
|
+
"""<p>Returns a database user name and temporary password with temporary authorization to log in to Amazon Redshift Serverless.</p> <p>By default, the temporary credentials expire in 900 seconds. You can optionally specify a duration between 900 seconds (15 minutes) and 3600 seconds (60 minutes).</p> <p>The Identity and Access Management (IAM) user or role that runs GetCredentials must have an IAM policy attached that allows access to all necessary actions and resources.</p> <p>If the <code>DbName</code> parameter is specified, the IAM policy must allow access to the resource dbname for the specified database name.</p>
|
|
522
522
|
|
|
523
523
|
Args:
|
|
524
|
-
db_name: <p>The name of the database to get temporary authorization to log on to.</p> <p>Constraints:</p> <ul> <li> <p>Must be 1 to 64 alphanumeric characters or hyphens.</p> </li> <li> <p>Must contain only uppercase or lowercase letters, numbers, underscore, plus sign, period (dot), at symbol (@), or hyphen.</p> </li> <li> <p>The first character must be a letter.</p> </li> <li> <p>Must not contain a colon ( : ) or slash ( / ).</p> </li> <li> <p>Cannot be a reserved word. A list of reserved words can be found in <a href
|
|
524
|
+
db_name: <p>The name of the database to get temporary authorization to log on to.</p> <p>Constraints:</p> <ul> <li> <p>Must be 1 to 64 alphanumeric characters or hyphens.</p> </li> <li> <p>Must contain only uppercase or lowercase letters, numbers, underscore, plus sign, period (dot), at symbol (@), or hyphen.</p> </li> <li> <p>The first character must be a letter.</p> </li> <li> <p>Must not contain a colon ( : ) or slash ( / ).</p> </li> <li> <p>Cannot be a reserved word. A list of reserved words can be found in <a href="https://docs.aws.amazon.com/redshift/latest/dg/r_pg_keywords.html">Reserved Words </a> in the Amazon Redshift Database Developer Guide</p> </li> </ul>
|
|
525
525
|
duration_seconds: <p>The number of seconds until the returned temporary password expires. The minimum is 900 seconds, and the maximum is 3600 seconds.</p>
|
|
526
526
|
workgroup_name: <p>The name of the workgroup associated with the database.</p>
|
|
527
527
|
custom_domain_name: <p>The custom domain name associated with the workgroup. The custom domain name or the workgroup name must be included in the request.</p>
|
|
@@ -999,7 +999,7 @@ class AsyncRedshiftServerlessClient:
|
|
|
999
999
|
|
|
1000
1000
|
Args:
|
|
1001
1001
|
resource_arn: <p>The Amazon Resource Name (ARN) of the account to create or update a resource policy for.</p>
|
|
1002
|
-
policy: <p>The policy to create or update. For example, the following policy grants a user authorization to restore a snapshot.</p> <p> <code
|
|
1002
|
+
policy: <p>The policy to create or update. For example, the following policy grants a user authorization to restore a snapshot.</p> <p> <code>"{\"Version\": \"2012-10-17\", \"Statement\" : [{ \"Sid\": \"AllowUserRestoreFromSnapshot\", \"Principal\":{\"AWS\": [\"739247239426\"]}, \"Action\": [\"redshift-serverless:RestoreFromSnapshot\"] , \"Effect\": \"Allow\" }]}"</code> </p>
|
|
1003
1003
|
|
|
1004
1004
|
Raises:
|
|
1005
1005
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -2070,13 +2070,13 @@ class AsyncRedshiftServerlessClient:
|
|
|
2070
2070
|
retention_period: Optional[int] = None,
|
|
2071
2071
|
tags: Optional["capo_redshift_serverless.types.tag_list.TagList"] = None,
|
|
2072
2072
|
) -> "capo_redshift_serverless.types.convert_recovery_point_to_snapshot_response.ConvertRecoveryPointToSnapshotResponse":
|
|
2073
|
-
|
|
2073
|
+
"""<p>Converts a recovery point to a snapshot. For more information about recovery points and snapshots, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-snapshots-recovery-points.html">Working with snapshots and recovery points</a>.</p>
|
|
2074
2074
|
|
|
2075
2075
|
Args:
|
|
2076
2076
|
recovery_point_id: <p>The unique identifier of the recovery point.</p>
|
|
2077
2077
|
snapshot_name: <p>The name of the snapshot.</p>
|
|
2078
2078
|
retention_period: <p>How long to retain the snapshot.</p>
|
|
2079
|
-
tags: <p>An array of <a href
|
|
2079
|
+
tags: <p>An array of <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_Tag.html">Tag objects</a> to associate with the created snapshot.</p>
|
|
2080
2080
|
|
|
2081
2081
|
Raises:
|
|
2082
2082
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -2411,12 +2411,12 @@ class AsyncRedshiftServerlessClient:
|
|
|
2411
2411
|
config_overrides: Optional[AsyncRedshiftServerlessClientConfig] = None,
|
|
2412
2412
|
client_token: Optional[str] = None,
|
|
2413
2413
|
) -> "capo_redshift_serverless.types.create_reservation_response.CreateReservationResponse":
|
|
2414
|
-
|
|
2414
|
+
"""<p>Creates an Amazon Redshift Serverless reservation, which gives you the option to commit to a specified number of Redshift Processing Units (RPUs) for a year at a discount from Serverless on-demand (OD) rates.</p>
|
|
2415
2415
|
|
|
2416
2416
|
Args:
|
|
2417
2417
|
capacity: <p>The number of Redshift Processing Units (RPUs) to reserve.</p>
|
|
2418
2418
|
offering_id: <p>The ID of the offering associated with the reservation. The offering determines the payment schedule for the reservation.</p>
|
|
2419
|
-
client_token: <p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. This token must be a valid UUIDv4 value. For more information about idempotency, see <a href
|
|
2419
|
+
client_token: <p>A unique, case-sensitive identifier that you provide to ensure the idempotency of the request. If not provided, the Amazon Web Services SDK populates this field. This token must be a valid UUIDv4 value. For more information about idempotency, see <a href="https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/"> Making retries safe with idempotent APIs </a>.</p>
|
|
2420
2420
|
|
|
2421
2421
|
Raises:
|
|
2422
2422
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -2721,14 +2721,14 @@ class AsyncRedshiftServerlessClient:
|
|
|
2721
2721
|
start_time: Optional[datetime.datetime] = None,
|
|
2722
2722
|
end_time: Optional[datetime.datetime] = None,
|
|
2723
2723
|
) -> "capo_redshift_serverless.types.create_scheduled_action_response.CreateScheduledActionResponse":
|
|
2724
|
-
|
|
2724
|
+
"""<p>Creates a scheduled action. A scheduled action contains a schedule and an Amazon Redshift API action. For example, you can create a schedule of when to run the <code>CreateSnapshot</code> API operation.</p>
|
|
2725
2725
|
|
|
2726
2726
|
Args:
|
|
2727
2727
|
scheduled_action_name: <p>The name of the scheduled action.</p>
|
|
2728
|
-
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code
|
|
2729
|
-
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots. (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href
|
|
2728
|
+
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code>"(0 10 ? * MON *)"</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions">Cron Expressions</a> in the <i>Amazon CloudWatch Events User Guide</i>.</p> </li> </ul>
|
|
2729
|
+
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots. (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html">Using Identity-Based Policies for Amazon Redshift</a> in the Amazon Redshift Management Guide</p>
|
|
2730
2730
|
namespace_name: <p>The name of the namespace for which to create a scheduled action.</p>
|
|
2731
|
-
enabled: <p>Indicates whether the schedule is enabled. If false, the scheduled action does not trigger. For more information about <code>state</code> of the scheduled action, see <a href
|
|
2731
|
+
enabled: <p>Indicates whether the schedule is enabled. If false, the scheduled action does not trigger. For more information about <code>state</code> of the scheduled action, see <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_ScheduledAction.html">ScheduledAction</a>.</p>
|
|
2732
2732
|
scheduled_action_description: <p>The description of the scheduled action.</p>
|
|
2733
2733
|
start_time: <p>The start time in UTC when the schedule is active. Before this time, the scheduled action does not trigger.</p>
|
|
2734
2734
|
end_time: <p>The end time in UTC when the schedule is no longer active. After this time, the scheduled action does not trigger.</p>
|
|
@@ -2976,12 +2976,12 @@ class AsyncRedshiftServerlessClient:
|
|
|
2976
2976
|
start_time: Optional[datetime.datetime] = None,
|
|
2977
2977
|
end_time: Optional[datetime.datetime] = None,
|
|
2978
2978
|
) -> "capo_redshift_serverless.types.update_scheduled_action_response.UpdateScheduledActionResponse":
|
|
2979
|
-
|
|
2979
|
+
"""<p>Updates a scheduled action.</p>
|
|
2980
2980
|
|
|
2981
2981
|
Args:
|
|
2982
2982
|
scheduled_action_name: <p>The name of the scheduled action to update to.</p>
|
|
2983
|
-
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code
|
|
2984
|
-
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href
|
|
2983
|
+
schedule: <p>The schedule for a one-time (at timestamp format) or recurring (cron format) scheduled action. Schedule invocations must be separated by at least one hour. Times are in UTC.</p> <ul> <li> <p>Format of at timestamp is <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2016-03-04T17:27:00</code>.</p> </li> <li> <p>Format of cron expression is <code>(Minutes Hours Day-of-month Month Day-of-week Year)</code>. For example, <code>"(0 10 ? * MON *)"</code>. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/ScheduledEvents.html#CronExpressions">Cron Expressions</a> in the <i>Amazon CloudWatch Events User Guide</i>.</p> </li> </ul>
|
|
2984
|
+
role_arn: <p>The ARN of the IAM role to assume to run the scheduled action. This IAM role must have permission to run the Amazon Redshift Serverless API operation in the scheduled action. This IAM role must allow the Amazon Redshift scheduler to schedule creating snapshots (Principal scheduler.redshift.amazonaws.com) to assume permissions on your behalf. For more information about the IAM role to use with the Amazon Redshift scheduler, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/redshift-iam-access-control-identity-based.html">Using Identity-Based Policies for Amazon Redshift</a> in the Amazon Redshift Management Guide</p>
|
|
2985
2985
|
enabled: <p>Specifies whether to enable the scheduled action.</p>
|
|
2986
2986
|
scheduled_action_description: <p>The descripion of the scheduled action to update to.</p>
|
|
2987
2987
|
start_time: <p>The start time in UTC of the scheduled action to update to.</p>
|
|
@@ -3048,13 +3048,13 @@ class AsyncRedshiftServerlessClient:
|
|
|
3048
3048
|
) -> (
|
|
3049
3049
|
"capo_redshift_serverless.types.create_snapshot_response.CreateSnapshotResponse"
|
|
3050
3050
|
):
|
|
3051
|
-
|
|
3051
|
+
"""<p>Creates a snapshot of all databases in a namespace. For more information about snapshots, see <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/serverless-snapshots-recovery-points.html"> Working with snapshots and recovery points</a>.</p>
|
|
3052
3052
|
|
|
3053
3053
|
Args:
|
|
3054
3054
|
namespace_name: <p>The namespace to create a snapshot for.</p>
|
|
3055
3055
|
snapshot_name: <p>The name of the snapshot.</p>
|
|
3056
3056
|
retention_period: <p>How long to retain the created snapshot.</p>
|
|
3057
|
-
tags: <p>An array of <a href
|
|
3057
|
+
tags: <p>An array of <a href="https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_Tag.html">Tag objects</a> to associate with the snapshot.</p>
|
|
3058
3058
|
|
|
3059
3059
|
Raises:
|
|
3060
3060
|
capo_redshift_serverless.errors.conflict_exception.ConflictException: <p>The submitted action has conflicts.</p>
|
|
@@ -3726,7 +3726,7 @@ class AsyncRedshiftServerlessClient:
|
|
|
3726
3726
|
target_schema_name: Optional[str] = None,
|
|
3727
3727
|
activate_case_sensitive_identifier: Optional[bool] = None,
|
|
3728
3728
|
) -> "capo_redshift_serverless.types.restore_table_from_snapshot_response.RestoreTableFromSnapshotResponse":
|
|
3729
|
-
|
|
3729
|
+
"""<p>Restores a table from a snapshot to your Amazon Redshift Serverless instance. You can't use this operation to restore tables with <a href="https://docs.aws.amazon.com/redshift/latest/dg/t_Sorting_data.html#t_Sorting_data-interleaved">interleaved sort keys</a>.</p>
|
|
3730
3730
|
|
|
3731
3731
|
Args:
|
|
3732
3732
|
namespace_name: <p>The namespace of the snapshot to restore from.</p>
|
|
@@ -4240,14 +4240,14 @@ class AsyncRedshiftServerlessClient:
|
|
|
4240
4240
|
] = None,
|
|
4241
4241
|
extra_compute_for_automatic_optimization: Optional[bool] = None,
|
|
4242
4242
|
) -> "capo_redshift_serverless.types.create_workgroup_response.CreateWorkgroupResponse":
|
|
4243
|
-
|
|
4243
|
+
"""<p>Creates an workgroup in Amazon Redshift Serverless.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a workgroup is in an account with VPC BPA turned on, the following capabilities are blocked: </p> <ul> <li> <p>Creating a public access workgroup</p> </li> <li> <p>Modifying a private workgroup to public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the workgroup when the workgroup is public</p> </li> </ul> <p>For more information about VPC BPA, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>
|
|
4244
4244
|
|
|
4245
4245
|
Args:
|
|
4246
4246
|
workgroup_name: <p>The name of the created workgroup.</p>
|
|
4247
4247
|
namespace_name: <p>The name of the namespace to associate with the workgroup.</p>
|
|
4248
4248
|
base_capacity: <p>The base data warehouse capacity of the workgroup in Redshift Processing Units (RPUs).</p>
|
|
4249
4249
|
enhanced_vpc_routing: <p>The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC instead of over the internet.</p>
|
|
4250
|
-
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href
|
|
4250
|
+
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href="https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html#cm-c-wlm-query-monitoring-metrics-serverless"> Query monitoring metrics for Amazon Redshift Serverless</a>.</p>
|
|
4251
4251
|
security_group_ids: <p>An array of security group IDs to associate with the workgroup.</p>
|
|
4252
4252
|
subnet_ids: <p>An array of VPC subnet IDs to associate with the workgroup.</p>
|
|
4253
4253
|
publicly_accessible: <p>A value that specifies whether the workgroup can be accessed from a public network.</p>
|
|
@@ -4403,13 +4403,13 @@ class AsyncRedshiftServerlessClient:
|
|
|
4403
4403
|
] = None,
|
|
4404
4404
|
extra_compute_for_automatic_optimization: Optional[bool] = None,
|
|
4405
4405
|
) -> "capo_redshift_serverless.types.update_workgroup_response.UpdateWorkgroupResponse":
|
|
4406
|
-
|
|
4406
|
+
"""<p>Updates a workgroup with the specified configuration settings. You can't update multiple parameters in one request. For example, you can update <code>baseCapacity</code> or <code>port</code> in a single request, but you can't update both in the same request.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a workgroup is in an account with VPC BPA turned on, the following capabilities are blocked: </p> <ul> <li> <p>Creating a public access workgroup</p> </li> <li> <p>Modifying a private workgroup to public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the workgroup when the workgroup is public</p> </li> </ul> <p>For more information about VPC BPA, see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>
|
|
4407
4407
|
|
|
4408
4408
|
Args:
|
|
4409
4409
|
workgroup_name: <p>The name of the workgroup to update. You can't update the name of a workgroup once it is created.</p>
|
|
4410
4410
|
base_capacity: <p>The new base data warehouse capacity in Redshift Processing Units (RPUs).</p>
|
|
4411
4411
|
enhanced_vpc_routing: <p>The value that specifies whether to turn on enhanced virtual private cloud (VPC) routing, which forces Amazon Redshift Serverless to route traffic through your VPC.</p>
|
|
4412
|
-
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href
|
|
4412
|
+
config_parameters: <p>An array of parameters to set for advanced control over a database. The options are <code>auto_mv</code>, <code>datestyle</code>, <code>enable_case_sensitive_identifier</code>, <code>enable_user_activity_logging</code>, <code>query_group</code>, <code>search_path</code>, <code>require_ssl</code>, <code>use_fips_ssl</code>, and either <code>wlm_json_configuration</code> or query monitoring metrics that let you define performance boundaries. You can either specify individual query monitoring metrics (such as <code>max_scan_row_count</code>, <code>max_query_execution_time</code>) or use <code>wlm_json_configuration</code> to define query queues with rules, but not both. If you're using <code>wlm_json_configuration</code>, the maximum size of <code>parameterValue</code> is 8000 characters. For more information about query monitoring rules and available metrics, see <a href="https://docs.aws.amazon.com/redshift/latest/dg/cm-c-wlm-query-monitoring-rules.html#cm-c-wlm-query-monitoring-metrics-serverless"> Query monitoring metrics for Amazon Redshift Serverless</a>.</p>
|
|
4413
4413
|
publicly_accessible: <p>A value that specifies whether the workgroup can be accessible from a public network.</p>
|
|
4414
4414
|
subnet_ids: <p>An array of VPC subnet IDs to associate with the workgroup.</p>
|
|
4415
4415
|
security_group_ids: <p>An array of security group IDs to associate with the workgroup.</p>
|