Skip to content

Commit

Permalink
Merge branch 'release-1.35.21'
Browse files Browse the repository at this point in the history
* release-1.35.21:
  Bumping version to 1.35.21
  Update to latest models
  • Loading branch information
aws-sdk-python-automation committed Sep 17, 2024
2 parents 40b28f4 + 41e4f43 commit c7615e4
Show file tree
Hide file tree
Showing 10 changed files with 474 additions and 99 deletions.
32 changes: 32 additions & 0 deletions .changes/1.35.21.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
[
{
"category": "``codebuild``",
"description": "GitLab Enhancements - Add support for Self-Hosted GitLab runners in CodeBuild. Add group webhooks",
"type": "api-change"
},
{
"category": "``ecr``",
"description": "The `DescribeImageScanning` API now includes `fixAvailable`, `exploitAvailable`, and `fixedInVersion` fields to provide more detailed information about the availability of fixes, exploits, and fixed versions for identified image vulnerabilities.",
"type": "api-change"
},
{
"category": "``ecs``",
"description": "This is a documentation only release to address various tickets.",
"type": "api-change"
},
{
"category": "``lambda``",
"description": "Support for JSON resource-based policies and block public access",
"type": "api-change"
},
{
"category": "``rds``",
"description": "Updates Amazon RDS documentation with configuration information about the BYOL model for RDS for Db2.",
"type": "api-change"
},
{
"category": "``ssm``",
"description": "Support for additional levels of cross-account, cross-Region organizational units in Automation. Various documentation updates.",
"type": "api-change"
}
]
11 changes: 11 additions & 0 deletions CHANGELOG.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,17 @@
CHANGELOG
=========

1.35.21
=======

* api-change:``codebuild``: GitLab Enhancements - Add support for Self-Hosted GitLab runners in CodeBuild. Add group webhooks
* api-change:``ecr``: The `DescribeImageScanning` API now includes `fixAvailable`, `exploitAvailable`, and `fixedInVersion` fields to provide more detailed information about the availability of fixes, exploits, and fixed versions for identified image vulnerabilities.
* api-change:``ecs``: This is a documentation only release to address various tickets.
* api-change:``lambda``: Support for JSON resource-based policies and block public access
* api-change:``rds``: Updates Amazon RDS documentation with configuration information about the BYOL model for RDS for Db2.
* api-change:``ssm``: Support for additional levels of cross-account, cross-Region organizational units in Automation. Various documentation updates.


1.35.20
=======

Expand Down
2 changes: 1 addition & 1 deletion botocore/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
import os
import re

__version__ = '1.35.20'
__version__ = '1.35.21'


class NullHandler(logging.Handler):
Expand Down
9 changes: 5 additions & 4 deletions botocore/data/codebuild/2016-10-06/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -3941,15 +3941,15 @@
"members":{
"name":{
"shape":"String",
"documentation":"<p>The name of either the enterprise or organization that will send webhook events to CodeBuild, depending on if the webhook is a global or organization webhook respectively.</p>"
"documentation":"<p>The name of either the group, enterprise, or organization that will send webhook events to CodeBuild, depending on the type of webhook.</p>"
},
"domain":{
"shape":"String",
"documentation":"<p>The domain of the GitHub Enterprise organization. Note that this parameter is only required if your project's source type is GITHUB_ENTERPRISE</p>"
"documentation":"<p>The domain of the GitHub Enterprise organization or the GitLab Self Managed group. Note that this parameter is only required if your project's source type is GITHUB_ENTERPRISE or GITLAB_SELF_MANAGED.</p>"
},
"scope":{
"shape":"WebhookScopeType",
"documentation":"<p>The type of scope for a GitHub webhook.</p>"
"documentation":"<p>The type of scope for a GitHub or GitLab webhook.</p>"
}
},
"documentation":"<p>Contains configuration information about the scope for a webhook. </p>"
Expand Down Expand Up @@ -4867,7 +4867,8 @@
"type":"string",
"enum":[
"GITHUB_ORGANIZATION",
"GITHUB_GLOBAL"
"GITHUB_GLOBAL",
"GITLAB_GROUP"
]
},
"WrapperBoolean":{"type":"boolean"},
Expand Down
17 changes: 16 additions & 1 deletion botocore/data/ecr/2015-09-21/service-2.json
Original file line number Diff line number Diff line change
Expand Up @@ -1806,7 +1806,7 @@
"members":{
"encryptionType":{
"shape":"EncryptionType",
"documentation":"<p>The encryption type to use.</p> <p>If you use the <code>KMS</code> encryption type, the contents of the repository will be encrypted using server-side encryption with Key Management Service key stored in KMS. When you use KMS to encrypt your data, you can either use the default Amazon Web Services managed KMS key for Amazon ECR, or specify your own KMS key, which you already created.</p> <p>If you use the <code>KMS_DSSE</code> encryption type, the contents of the repository will be encrypted with two layers of encryption using server-side encryption with the KMS Management Service key stored in KMS. Similar to the KMS encryption type, you can either use the default Amazon Web Services managed KMS key for Amazon ECR, or specify your own KMS key, which you've already created. </p> <p>If you use the <code>AES256</code> encryption type, Amazon ECR uses server-side encryption with Amazon S3-managed encryption keys which encrypts the images in the repository using an AES256 encryption algorithm. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Protecting data using server-side encryption with Amazon S3-managed encryption keys (SSE-S3)</a> in the <i>Amazon Simple Storage Service Console Developer Guide</i>.</p>"
"documentation":"<p>The encryption type to use.</p> <p>If you use the <code>KMS</code> encryption type, the contents of the repository will be encrypted using server-side encryption with Key Management Service key stored in KMS. When you use KMS to encrypt your data, you can either use the default Amazon Web Services managed KMS key for Amazon ECR, or specify your own KMS key, which you already created.</p> <p>If you use the <code>KMS_DSSE</code> encryption type, the contents of the repository will be encrypted with two layers of encryption using server-side encryption with the KMS Management Service key stored in KMS. Similar to the <code>KMS</code> encryption type, you can either use the default Amazon Web Services managed KMS key for Amazon ECR, or specify your own KMS key, which you've already created. </p> <p>If you use the <code>AES256</code> encryption type, Amazon ECR uses server-side encryption with Amazon S3-managed encryption keys which encrypts the images in the repository using an AES256 encryption algorithm.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html\">Amazon ECR encryption at rest</a> in the <i>Amazon Elastic Container Registry User Guide</i>.</p>"
},
"kmsKey":{
"shape":"KmsKey",
Expand Down Expand Up @@ -1900,6 +1900,14 @@
"updatedAt":{
"shape":"Date",
"documentation":"<p>The date and time the finding was last updated at.</p>"
},
"fixAvailable":{
"shape":"FixAvailable",
"documentation":"<p>Details on whether a fix is available through a version update. This value can be <code>YES</code>, <code>NO</code>, or <code>PARTIAL</code>. A <code>PARTIAL</code> fix means that some, but not all, of the packages identified in the finding have fixes available through updated versions.</p>"
},
"exploitAvailable":{
"shape":"ExploitAvailable",
"documentation":"<p>If a finding discovered in your environment has an exploit available.</p>"
}
},
"documentation":"<p>The details of an enhanced image scan. This is returned when enhanced scanning is enabled for your private registry.</p>"
Expand All @@ -1912,6 +1920,7 @@
"EvaluationTimestamp":{"type":"timestamp"},
"ExceptionMessage":{"type":"string"},
"ExpirationTimestamp":{"type":"timestamp"},
"ExploitAvailable":{"type":"string"},
"FilePath":{"type":"string"},
"FindingArn":{"type":"string"},
"FindingDescription":{"type":"string"},
Expand All @@ -1932,6 +1941,8 @@
"key":{"shape":"FindingSeverity"},
"value":{"shape":"SeverityCount"}
},
"FixAvailable":{"type":"string"},
"FixedInVersion":{"type":"string"},
"ForceFlag":{"type":"boolean"},
"GetAccountSettingRequest":{
"type":"structure",
Expand Down Expand Up @@ -4466,6 +4477,10 @@
"version":{
"shape":"Version",
"documentation":"<p>The version of the vulnerable package.</p>"
},
"fixedInVersion":{
"shape":"FixedInVersion",
"documentation":"<p>The version of the package that contains the vulnerability fix.</p>"
}
},
"documentation":"<p>Information on the vulnerable package identified by a finding.</p>"
Expand Down
Loading

0 comments on commit c7615e4

Please sign in to comment.