Skip to content

Commit 423b0b0

Browse files
feat(iam): update the api
#### iam:v1 The following keys were deleted: - resources.projects.resources.serviceAccounts.resources.keys.methods.patch (Total Keys: 12) - schemas.PatchServiceAccountKeyRequest (Total Keys: 5) - schemas.ServiceAccountKey.properties.contact.type (Total Keys: 1) - schemas.ServiceAccountKey.properties.creator (Total Keys: 2)
1 parent 740ff2a commit 423b0b0

File tree

4 files changed

+3
-142
lines changed

4 files changed

+3
-142
lines changed

docs/dyn/iam_v1.projects.serviceAccounts.keys.html

Lines changed: 0 additions & 82 deletions
Original file line numberDiff line numberDiff line change
@@ -95,9 +95,6 @@ <h2>Instance Methods</h2>
9595
<p class="toc_element">
9696
<code><a href="#list">list(name, keyTypes=None, x__xgafv=None)</a></code></p>
9797
<p class="firstline">Lists every ServiceAccountKey for a service account.</p>
98-
<p class="toc_element">
99-
<code><a href="#patch">patch(name, body=None, x__xgafv=None)</a></code></p>
100-
<p class="firstline">Patches a ServiceAccountKey.</p>
10198
<p class="toc_element">
10299
<code><a href="#upload">upload(name, body=None, x__xgafv=None)</a></code></p>
103100
<p class="firstline">Uploads the public key portion of a key pair that you manage, and associates the public key with a ServiceAccount. After you upload the public key, you can use the private key from the key pair as a service account key.</p>
@@ -130,9 +127,6 @@ <h3>Method Details</h3>
130127
An object of the form:
131128

132129
{ # Represents a service account key. A service account has two sets of key-pairs: user-managed, and system-managed. User-managed key-pairs can be created and deleted by users. Users are responsible for rotating these keys periodically to ensure security of their service accounts. Users retain the private key of these key-pairs, and Google retains ONLY the public key. System-managed keys are automatically rotated by Google, and are used for signing for a maximum of two weeks. The rotation process is probabilistic, and usage of the new key will gradually ramp up and down over the key&#x27;s lifetime. If you cache the public key set for a service account, we recommend that you update the cache every 15 minutes. User-managed keys can be added and removed at any time, so it is important to update the cache frequently. For Google-managed keys, Google will publish a key at least 6 hours before it is first used for signing and will keep publishing it for at least 6 hours after it was last used for signing. Public keys for all service accounts are also published at the OAuth2 Service Account API.
133-
&quot;contact&quot;: &quot;A String&quot;, # Optional. A user provided email address as the point of contact for this service account key. Must be an email address. Limit 64 characters.
134-
&quot;creator&quot;: &quot;A String&quot;, # Output only. The cloud identity that created this service account key. Populated automatically when the key is created and not editable by the user.
135-
&quot;description&quot;: &quot;A String&quot;, # Optional. A user provided description of this service account key.
136130
&quot;disableReason&quot;: &quot;A String&quot;, # Output only. optional. If the key is disabled, it may have a DisableReason describing why it was disabled.
137131
&quot;disabled&quot;: True or False, # The key status.
138132
&quot;extendedStatus&quot;: [ # Output only. Extended Status provides permanent information about a service account key. For example, if this key was detected as exposed or compromised, that information will remain for the lifetime of the key in the extended_status.
@@ -241,9 +235,6 @@ <h3>Method Details</h3>
241235
An object of the form:
242236

243237
{ # Represents a service account key. A service account has two sets of key-pairs: user-managed, and system-managed. User-managed key-pairs can be created and deleted by users. Users are responsible for rotating these keys periodically to ensure security of their service accounts. Users retain the private key of these key-pairs, and Google retains ONLY the public key. System-managed keys are automatically rotated by Google, and are used for signing for a maximum of two weeks. The rotation process is probabilistic, and usage of the new key will gradually ramp up and down over the key&#x27;s lifetime. If you cache the public key set for a service account, we recommend that you update the cache every 15 minutes. User-managed keys can be added and removed at any time, so it is important to update the cache frequently. For Google-managed keys, Google will publish a key at least 6 hours before it is first used for signing and will keep publishing it for at least 6 hours after it was last used for signing. Public keys for all service accounts are also published at the OAuth2 Service Account API.
244-
&quot;contact&quot;: &quot;A String&quot;, # Optional. A user provided email address as the point of contact for this service account key. Must be an email address. Limit 64 characters.
245-
&quot;creator&quot;: &quot;A String&quot;, # Output only. The cloud identity that created this service account key. Populated automatically when the key is created and not editable by the user.
246-
&quot;description&quot;: &quot;A String&quot;, # Optional. A user provided description of this service account key.
247238
&quot;disableReason&quot;: &quot;A String&quot;, # Output only. optional. If the key is disabled, it may have a DisableReason describing why it was disabled.
248239
&quot;disabled&quot;: True or False, # The key status.
249240
&quot;extendedStatus&quot;: [ # Output only. Extended Status provides permanent information about a service account key. For example, if this key was detected as exposed or compromised, that information will remain for the lifetime of the key in the extended_status.
@@ -286,9 +277,6 @@ <h3>Method Details</h3>
286277
{ # The service account keys list response.
287278
&quot;keys&quot;: [ # The public keys for the service account.
288279
{ # Represents a service account key. A service account has two sets of key-pairs: user-managed, and system-managed. User-managed key-pairs can be created and deleted by users. Users are responsible for rotating these keys periodically to ensure security of their service accounts. Users retain the private key of these key-pairs, and Google retains ONLY the public key. System-managed keys are automatically rotated by Google, and are used for signing for a maximum of two weeks. The rotation process is probabilistic, and usage of the new key will gradually ramp up and down over the key&#x27;s lifetime. If you cache the public key set for a service account, we recommend that you update the cache every 15 minutes. User-managed keys can be added and removed at any time, so it is important to update the cache frequently. For Google-managed keys, Google will publish a key at least 6 hours before it is first used for signing and will keep publishing it for at least 6 hours after it was last used for signing. Public keys for all service accounts are also published at the OAuth2 Service Account API.
289-
&quot;contact&quot;: &quot;A String&quot;, # Optional. A user provided email address as the point of contact for this service account key. Must be an email address. Limit 64 characters.
290-
&quot;creator&quot;: &quot;A String&quot;, # Output only. The cloud identity that created this service account key. Populated automatically when the key is created and not editable by the user.
291-
&quot;description&quot;: &quot;A String&quot;, # Optional. A user provided description of this service account key.
292280
&quot;disableReason&quot;: &quot;A String&quot;, # Output only. optional. If the key is disabled, it may have a DisableReason describing why it was disabled.
293281
&quot;disabled&quot;: True or False, # The key status.
294282
&quot;extendedStatus&quot;: [ # Output only. Extended Status provides permanent information about a service account key. For example, if this key was detected as exposed or compromised, that information will remain for the lifetime of the key in the extended_status.
@@ -311,73 +299,6 @@ <h3>Method Details</h3>
311299
}</pre>
312300
</div>
313301

314-
<div class="method">
315-
<code class="details" id="patch">patch(name, body=None, x__xgafv=None)</code>
316-
<pre>Patches a ServiceAccountKey.
317-
318-
Args:
319-
name: string, The resource name of the service account key in the following format `projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT}/keys/{key}`. (required)
320-
body: object, The request body.
321-
The object takes the form of:
322-
323-
{ # The service account key patch request.
324-
&quot;serviceAccountKey&quot;: { # Represents a service account key. A service account has two sets of key-pairs: user-managed, and system-managed. User-managed key-pairs can be created and deleted by users. Users are responsible for rotating these keys periodically to ensure security of their service accounts. Users retain the private key of these key-pairs, and Google retains ONLY the public key. System-managed keys are automatically rotated by Google, and are used for signing for a maximum of two weeks. The rotation process is probabilistic, and usage of the new key will gradually ramp up and down over the key&#x27;s lifetime. If you cache the public key set for a service account, we recommend that you update the cache every 15 minutes. User-managed keys can be added and removed at any time, so it is important to update the cache frequently. For Google-managed keys, Google will publish a key at least 6 hours before it is first used for signing and will keep publishing it for at least 6 hours after it was last used for signing. Public keys for all service accounts are also published at the OAuth2 Service Account API. # Required. The service account key to update.
325-
&quot;contact&quot;: &quot;A String&quot;, # Optional. A user provided email address as the point of contact for this service account key. Must be an email address. Limit 64 characters.
326-
&quot;creator&quot;: &quot;A String&quot;, # Output only. The cloud identity that created this service account key. Populated automatically when the key is created and not editable by the user.
327-
&quot;description&quot;: &quot;A String&quot;, # Optional. A user provided description of this service account key.
328-
&quot;disableReason&quot;: &quot;A String&quot;, # Output only. optional. If the key is disabled, it may have a DisableReason describing why it was disabled.
329-
&quot;disabled&quot;: True or False, # The key status.
330-
&quot;extendedStatus&quot;: [ # Output only. Extended Status provides permanent information about a service account key. For example, if this key was detected as exposed or compromised, that information will remain for the lifetime of the key in the extended_status.
331-
{ # Extended status can store additional metadata. For example, for keys disabled due to their private key data being expoesed we may include a message with more information about the exposure.
332-
&quot;key&quot;: &quot;A String&quot;, # The key for this extended status.
333-
&quot;value&quot;: &quot;A String&quot;, # The value for the extended status.
334-
},
335-
],
336-
&quot;keyAlgorithm&quot;: &quot;A String&quot;, # Specifies the algorithm (and possibly key size) for the key.
337-
&quot;keyOrigin&quot;: &quot;A String&quot;, # The key origin.
338-
&quot;keyType&quot;: &quot;A String&quot;, # The key type.
339-
&quot;name&quot;: &quot;A String&quot;, # The resource name of the service account key in the following format `projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT}/keys/{key}`.
340-
&quot;privateKeyData&quot;: &quot;A String&quot;, # The private key data. Only provided in `CreateServiceAccountKey` responses. Make sure to keep the private key data secure because it allows for the assertion of the service account identity. When base64 decoded, the private key data can be used to authenticate with Google API client libraries and with gcloud auth activate-service-account.
341-
&quot;privateKeyType&quot;: &quot;A String&quot;, # The output format for the private key. Only provided in `CreateServiceAccountKey` responses, not in `GetServiceAccountKey` or `ListServiceAccountKey` responses. Google never exposes system-managed private keys, and never retains user-managed private keys.
342-
&quot;publicKeyData&quot;: &quot;A String&quot;, # The public key data. Only provided in `GetServiceAccountKey` responses.
343-
&quot;validAfterTime&quot;: &quot;A String&quot;, # The key can be used after this timestamp.
344-
&quot;validBeforeTime&quot;: &quot;A String&quot;, # The key can be used before this timestamp. For system-managed key pairs, this timestamp is the end time for the private key signing operation. The public key could still be used for verification for a few hours after this time.
345-
},
346-
&quot;updateMask&quot;: &quot;A String&quot;, # Required. The update mask to apply to the service account key. Only the following fields are eligible for patching: - contact - description
347-
}
348-
349-
x__xgafv: string, V1 error format.
350-
Allowed values
351-
1 - v1 error format
352-
2 - v2 error format
353-
354-
Returns:
355-
An object of the form:
356-
357-
{ # Represents a service account key. A service account has two sets of key-pairs: user-managed, and system-managed. User-managed key-pairs can be created and deleted by users. Users are responsible for rotating these keys periodically to ensure security of their service accounts. Users retain the private key of these key-pairs, and Google retains ONLY the public key. System-managed keys are automatically rotated by Google, and are used for signing for a maximum of two weeks. The rotation process is probabilistic, and usage of the new key will gradually ramp up and down over the key&#x27;s lifetime. If you cache the public key set for a service account, we recommend that you update the cache every 15 minutes. User-managed keys can be added and removed at any time, so it is important to update the cache frequently. For Google-managed keys, Google will publish a key at least 6 hours before it is first used for signing and will keep publishing it for at least 6 hours after it was last used for signing. Public keys for all service accounts are also published at the OAuth2 Service Account API.
358-
&quot;contact&quot;: &quot;A String&quot;, # Optional. A user provided email address as the point of contact for this service account key. Must be an email address. Limit 64 characters.
359-
&quot;creator&quot;: &quot;A String&quot;, # Output only. The cloud identity that created this service account key. Populated automatically when the key is created and not editable by the user.
360-
&quot;description&quot;: &quot;A String&quot;, # Optional. A user provided description of this service account key.
361-
&quot;disableReason&quot;: &quot;A String&quot;, # Output only. optional. If the key is disabled, it may have a DisableReason describing why it was disabled.
362-
&quot;disabled&quot;: True or False, # The key status.
363-
&quot;extendedStatus&quot;: [ # Output only. Extended Status provides permanent information about a service account key. For example, if this key was detected as exposed or compromised, that information will remain for the lifetime of the key in the extended_status.
364-
{ # Extended status can store additional metadata. For example, for keys disabled due to their private key data being expoesed we may include a message with more information about the exposure.
365-
&quot;key&quot;: &quot;A String&quot;, # The key for this extended status.
366-
&quot;value&quot;: &quot;A String&quot;, # The value for the extended status.
367-
},
368-
],
369-
&quot;keyAlgorithm&quot;: &quot;A String&quot;, # Specifies the algorithm (and possibly key size) for the key.
370-
&quot;keyOrigin&quot;: &quot;A String&quot;, # The key origin.
371-
&quot;keyType&quot;: &quot;A String&quot;, # The key type.
372-
&quot;name&quot;: &quot;A String&quot;, # The resource name of the service account key in the following format `projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT}/keys/{key}`.
373-
&quot;privateKeyData&quot;: &quot;A String&quot;, # The private key data. Only provided in `CreateServiceAccountKey` responses. Make sure to keep the private key data secure because it allows for the assertion of the service account identity. When base64 decoded, the private key data can be used to authenticate with Google API client libraries and with gcloud auth activate-service-account.
374-
&quot;privateKeyType&quot;: &quot;A String&quot;, # The output format for the private key. Only provided in `CreateServiceAccountKey` responses, not in `GetServiceAccountKey` or `ListServiceAccountKey` responses. Google never exposes system-managed private keys, and never retains user-managed private keys.
375-
&quot;publicKeyData&quot;: &quot;A String&quot;, # The public key data. Only provided in `GetServiceAccountKey` responses.
376-
&quot;validAfterTime&quot;: &quot;A String&quot;, # The key can be used after this timestamp.
377-
&quot;validBeforeTime&quot;: &quot;A String&quot;, # The key can be used before this timestamp. For system-managed key pairs, this timestamp is the end time for the private key signing operation. The public key could still be used for verification for a few hours after this time.
378-
}</pre>
379-
</div>
380-
381302
<div class="method">
382303
<code class="details" id="upload">upload(name, body=None, x__xgafv=None)</code>
383304
<pre>Uploads the public key portion of a key pair that you manage, and associates the public key with a ServiceAccount. After you upload the public key, you can use the private key from the key pair as a service account key.
@@ -400,9 +321,6 @@ <h3>Method Details</h3>
400321
An object of the form:
401322

402323
{ # Represents a service account key. A service account has two sets of key-pairs: user-managed, and system-managed. User-managed key-pairs can be created and deleted by users. Users are responsible for rotating these keys periodically to ensure security of their service accounts. Users retain the private key of these key-pairs, and Google retains ONLY the public key. System-managed keys are automatically rotated by Google, and are used for signing for a maximum of two weeks. The rotation process is probabilistic, and usage of the new key will gradually ramp up and down over the key&#x27;s lifetime. If you cache the public key set for a service account, we recommend that you update the cache every 15 minutes. User-managed keys can be added and removed at any time, so it is important to update the cache frequently. For Google-managed keys, Google will publish a key at least 6 hours before it is first used for signing and will keep publishing it for at least 6 hours after it was last used for signing. Public keys for all service accounts are also published at the OAuth2 Service Account API.
403-
&quot;contact&quot;: &quot;A String&quot;, # Optional. A user provided email address as the point of contact for this service account key. Must be an email address. Limit 64 characters.
404-
&quot;creator&quot;: &quot;A String&quot;, # Output only. The cloud identity that created this service account key. Populated automatically when the key is created and not editable by the user.
405-
&quot;description&quot;: &quot;A String&quot;, # Optional. A user provided description of this service account key.
406324
&quot;disableReason&quot;: &quot;A String&quot;, # Output only. optional. If the key is disabled, it may have a DisableReason describing why it was disabled.
407325
&quot;disabled&quot;: True or False, # The key status.
408326
&quot;extendedStatus&quot;: [ # Output only. Extended Status provides permanent information about a service account key. For example, if this key was detected as exposed or compromised, that information will remain for the lifetime of the key in the extended_status.

0 commit comments

Comments
 (0)