@ibm-cloud/secrets-manager 2.0.0 → 2.0.1

package/secrets-manager/v2.d.ts

@@ -266,6 +266,25 @@ declare class SecretsManagerV2 extends BaseService {
      * @returns {Promise<SecretsManagerV2.Response<SecretsManagerV2.SecretAction>>}
      */
     createSecretAction(params: SecretsManagerV2.CreateSecretActionParams): Promise<SecretsManagerV2.Response<SecretsManagerV2.SecretAction>>;
+    /**
+     * Get a secret by name.
+     *
+     * Get a secret and its details by specifying the Name and Type of the secret.
+     *
+     * A successful request returns the secret data that is associated with your secret, along with other metadata. To
+     * view only the details of a specified secret without retrieving its value, use the [Get secret
+     * metadata](#get-secret-metadata) operation.
+     *
+     * @param {Object} params - The parameters to send to the service.
+     * @param {string} params.secretType - The secret type. Supported types are arbitrary, certificates (imported, public,
+     * and private), IAM credentials, key-value, and user credentials.
+     * @param {string} params.name - A human-readable name to assign to your secret. To protect your privacy, do not use
+     * personal data, such as your name or location, as a name for your secret.
+     * @param {string} params.secretGroupName - The name of your secret group.
+     * @param {OutgoingHttpHeaders} [params.headers] - Custom request headers
+     * @returns {Promise<SecretsManagerV2.Response<SecretsManagerV2.Secret>>}
+     */
+    getSecretByNameType(params: SecretsManagerV2.GetSecretByNameTypeParams): Promise<SecretsManagerV2.Response<SecretsManagerV2.Secret>>;
     /*************************
      * secretVersions
      ************************/
@@ -630,7 +649,7 @@ declare class SecretsManagerV2 extends BaseService {
      * more of the fields: `name`, `config_type`, `secret_type`.
      *
      * **Usage:** If you want to list only the configurations that contain the string `text`, use
-     * `../secrets?search=text`.
+     * `../configurations?search=text`.
      * @param {OutgoingHttpHeaders} [params.headers] - Custom request headers
      * @returns {Promise<SecretsManagerV2.Response<SecretsManagerV2.ConfigurationMetadataPaginatedCollection>>}
      */
@@ -908,6 +927,33 @@ declare namespace SecretsManagerV2 {
         secretActionPrototype: SecretActionPrototype;
         headers?: OutgoingHttpHeaders;
     }
+    /** Parameters for the `getSecretByNameType` operation. */
+    interface GetSecretByNameTypeParams {
+        /** The secret type. Supported types are arbitrary, certificates (imported, public, and private), IAM
+         *  credentials, key-value, and user credentials.
+         */
+        secretType: GetSecretByNameTypeConstants.SecretType | string;
+        /** A human-readable name to assign to your secret. To protect your privacy, do not use personal data, such as
+         *  your name or location, as a name for your secret.
+         */
+        name: string;
+        /** The name of your secret group. */
+        secretGroupName: string;
+        headers?: OutgoingHttpHeaders;
+    }
+    /** Constants for the `getSecretByNameType` operation. */
+    namespace GetSecretByNameTypeConstants {
+        /** The secret type. Supported types are arbitrary, certificates (imported, public, and private), IAM credentials, key-value, and user credentials. */
+        enum SecretType {
+            ARBITRARY = "arbitrary",
+            IMPORTED_CERT = "imported_cert",
+            PUBLIC_CERT = "public_cert",
+            IAM_CREDENTIALS = "iam_credentials",
+            KV = "kv",
+            USERNAME_PASSWORD = "username_password",
+            PRIVATE_CERT = "private_cert"
+        }
+    }
     /** Parameters for the `createSecretVersion` operation. */
     interface CreateSecretVersionParams {
         /** The v4 UUID that uniquely identifies your secret. */
@@ -1189,7 +1235,7 @@ declare namespace SecretsManagerV2 {
          *  `name`, `config_type`, `secret_type`.
          *
          *  **Usage:** If you want to list only the configurations that contain the string `text`, use
-         *  `../secrets?search=text`.
+         *  `../configurations?search=text`.
          */
         search?: string;
         headers?: OutgoingHttpHeaders;
@@ -1429,7 +1475,7 @@ declare namespace SecretsManagerV2 {
          */
         rotate_keys?: boolean;
     }
-    /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+    /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types: username_password, private_cert, public_cert, iam_credentials. */
     interface RotationPolicy {
     }
     /** Your secret. */
@@ -1701,7 +1747,9 @@ declare namespace SecretsManagerV2 {
         updated_at: string;
         /** The number of versions of your secret. */
         versions_total: number;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The secret data that is assigned to an `arbitrary` secret. */
         payload?: string;
@@ -1755,7 +1803,9 @@ declare namespace SecretsManagerV2 {
         updated_at: string;
         /** The number of versions of your secret. */
         versions_total: number;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
     }
     /** ArbitrarySecretMetadataPatch. */
@@ -1780,7 +1830,9 @@ declare namespace SecretsManagerV2 {
         labels?: string[];
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
     }
     /** ArbitrarySecretPrototype. */
@@ -1793,7 +1845,9 @@ declare namespace SecretsManagerV2 {
          *  secret group.
          */
         description?: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** Labels that you can use to search secrets in your instance. Only 30 labels can be created.
          *
@@ -1850,7 +1904,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The secret data that is assigned to an `arbitrary` secret. */
         payload?: string;
@@ -1887,7 +1943,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
     }
     /** ArbitrarySecretVersionPrototype. */
@@ -1928,10 +1986,10 @@ declare namespace SecretsManagerV2 {
         created_at: string;
         /** The date when a resource was modified. The date format follows `RFC 3339`. */
         updated_at: string;
-        /** The API key that is generated for this secret.
-         *
-         *  After the secret reaches the end of its lease (see the `ttl` field), the API key is deleted automatically. If
-         *  you want to continue to use the same API key for future read operations, see the `reuse_api_key` field.
+        /** An IBM Cloud API key that can create and manage service IDs. The API key must be assigned the Editor
+         *  platform role on the Access Groups Service and the Operator platform role on the IAM Identity Service.  For more
+         *  information, see the
+         *  [docs](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-configure-iam-engine).
          */
         api_key?: string;
     }
@@ -1954,10 +2012,10 @@ declare namespace SecretsManagerV2 {
     }
     /** The configuration update of the IAM Credentials engine. */
     interface IAMCredentialsConfigurationPatch extends ConfigurationPatch {
-        /** The API key that is generated for this secret.
-         *
-         *  After the secret reaches the end of its lease (see the `ttl` field), the API key is deleted automatically. If
-         *  you want to continue to use the same API key for future read operations, see the `reuse_api_key` field.
+        /** An IBM Cloud API key that can create and manage service IDs. The API key must be assigned the Editor
+         *  platform role on the Access Groups Service and the Operator platform role on the IAM Identity Service.  For more
+         *  information, see the
+         *  [docs](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-configure-iam-engine).
          */
         api_key: string;
     }
@@ -1970,11 +2028,7 @@ declare namespace SecretsManagerV2 {
         name: string;
         /** The configuration type. */
         config_type: string;
-        /** The API key that is generated for this secret.
-         *
-         *  After the secret reaches the end of its lease (see the `ttl` field), the API key is deleted automatically. If
-         *  you want to continue to use the same API key for future read operations, see the `reuse_api_key` field.
-         */
+        /** The API key that is used to set the iam_credentials engine. */
         api_key: string;
     }
     /** Your IAM credentials secret. */
@@ -2065,7 +2119,9 @@ declare namespace SecretsManagerV2 {
          *  and API key are generated each time that the secret is read or accessed.
          */
         reuse_api_key: boolean;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The date that the secret is scheduled for automatic rotation.
          *
@@ -2168,7 +2224,9 @@ declare namespace SecretsManagerV2 {
          *  and API key are generated each time that the secret is read or accessed.
          */
         reuse_api_key: boolean;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The date that the secret is scheduled for automatic rotation.
          *
@@ -2208,7 +2266,9 @@ declare namespace SecretsManagerV2 {
          *  The minimum duration is 1 minute. The maximum is 90 days.
          */
         ttl?: string;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
     }
     /** IAMCredentialsSecretPrototype. */
@@ -2268,7 +2328,9 @@ declare namespace SecretsManagerV2 {
          *  and API key are generated each time that the secret is read or accessed.
          */
         reuse_api_key: boolean;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
@@ -2446,7 +2508,9 @@ declare namespace SecretsManagerV2 {
         alt_names?: string[];
         /** The Common Name (CN) represents the server name protected by the SSL certificate. */
         common_name?: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** Indicates whether the certificate was imported with an associated intermediate certificate. */
         intermediate_included: boolean;
@@ -2532,7 +2596,9 @@ declare namespace SecretsManagerV2 {
         alt_names?: string[];
         /** The Common Name (CN) represents the server name protected by the SSL certificate. */
         common_name?: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** Indicates whether the certificate was imported with an associated intermediate certificate. */
         intermediate_included: boolean;
@@ -2645,7 +2711,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number: string;
@@ -2694,7 +2762,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number: string;
@@ -3016,7 +3086,9 @@ declare namespace SecretsManagerV2 {
         certificate_template: string;
         /** The Common Name (CN) represents the server name that is protected by the SSL certificate. */
         common_name: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** The distinguished name that identifies the entity that signed and issued the certificate. */
         issuer: string;
@@ -3030,7 +3102,9 @@ declare namespace SecretsManagerV2 {
          *  for secrets that can be auto-rotated and an existing rotation policy.
          */
         next_rotation_date?: string;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number: string;
@@ -3153,7 +3227,7 @@ declare namespace SecretsManagerV2 {
          *  1) Subject information, including names and alternate names, are preserved from the CSR rather than by using the
          *  values that are provided in the other parameters to this operation.
          *
-         *  2) Any key usage, for example, nonrepudiation, that is requested in the CSR are added to the basic set of key
+         *  2) Any key usage, for example, non-repudiation, that is requested in the CSR are added to the basic set of key
          *  usages used for CA certificates that are signed by the intermediate authority.
          *
          *  3) Extensions that are requested in the CSR are copied into the issued private certificate.
@@ -3173,8 +3247,11 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
+        /** The requested value for the [`serialNumber`](https://datatracker.ietf.org/doc/html/rfc4519#section-2.31)
+         *  attribute that is in the certificate's distinguished name (DN).
+         *
+         *  **Note:** This field is not related to the `serial_number` field that is returned in the API response. The
+         *  `serial_number` field represents the certificate's randomly assigned serial number.
          */
         serial_number?: string;
         /** The type of configuration action. */
@@ -3234,7 +3311,7 @@ declare namespace SecretsManagerV2 {
          *  1) Subject information, including names and alternate names, are preserved from the CSR rather than by using the
          *  values that are provided in the other parameters to this operation.
          *
-         *  2) Any key usage, for example, nonrepudiation, that is requested in the CSR are added to the basic set of key
+         *  2) Any key usage, for example, non-repudiation, that is requested in the CSR are added to the basic set of key
          *  usages used for CA certificates that are signed by the intermediate authority.
          *
          *  3) Extensions that are requested in the CSR are copied into the issued private certificate.
@@ -3254,8 +3331,11 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
+        /** The requested value for the [`serialNumber`](https://datatracker.ietf.org/doc/html/rfc4519#section-2.31)
+         *  attribute that is in the certificate's distinguished name (DN).
+         *
+         *  **Note:** This field is not related to the `serial_number` field that is returned in the API response. The
+         *  `serial_number` field represents the certificate's randomly assigned serial number.
          */
         serial_number?: string;
         /** The type of configuration action. */
@@ -3313,7 +3393,7 @@ declare namespace SecretsManagerV2 {
          *  1) Subject information, including names and alternate names, are preserved from the CSR rather than by using the
          *  values that are provided in the other parameters to this operation.
          *
-         *  2) Any key usage, for example, nonrepudiation, that is requested in the CSR are added to the basic set of key
+         *  2) Any key usage, for example, non-repudiation, that is requested in the CSR are added to the basic set of key
          *  usages used for CA certificates that are signed by the intermediate authority.
          *
          *  3) Extensions that are requested in the CSR are copied into the issued private certificate.
@@ -3333,8 +3413,11 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
+        /** The requested value for the [`serialNumber`](https://datatracker.ietf.org/doc/html/rfc4519#section-2.31)
+         *  attribute that is in the certificate's distinguished name (DN).
+         *
+         *  **Note:** This field is not related to the `serial_number` field that is returned in the API response. The
+         *  `serial_number` field represents the certificate's randomly assigned serial number.
          */
         serial_number?: string;
         /** The type of configuration action. */
@@ -3392,7 +3475,7 @@ declare namespace SecretsManagerV2 {
          *  1) Subject information, including names and alternate names, are preserved from the CSR rather than by using the
          *  values that are provided in the other parameters to this operation.
          *
-         *  2) Any key usage, for example, nonrepudiation, that is requested in the CSR are added to the basic set of key
+         *  2) Any key usage, for example, non-repudiation, that is requested in the CSR are added to the basic set of key
          *  usages used for CA certificates that are signed by the intermediate authority.
          *
          *  3) Extensions that are requested in the CSR are copied into the issued private certificate.
@@ -3412,8 +3495,11 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
+        /** The requested value for the [`serialNumber`](https://datatracker.ietf.org/doc/html/rfc4519#section-2.31)
+         *  attribute that is in the certificate's distinguished name (DN).
+         *
+         *  **Note:** This field is not related to the `serial_number` field that is returned in the API response. The
+         *  `serial_number` field represents the certificate's randomly assigned serial number.
          */
         serial_number?: string;
         /** The type of configuration action. */
@@ -3454,7 +3540,9 @@ declare namespace SecretsManagerV2 {
          *  certificates that are issued by this certificate authority.
          */
         crl_distribution_points_encoded?: boolean;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The distinguished name that identifies the entity that signed and issued the certificate. */
         issuer?: string;
@@ -3531,9 +3619,7 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
-         */
+        /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number?: string;
         /** The configuration data of your Private Certificate. */
         data?: PrivateCertificateCAData;
@@ -3573,7 +3659,9 @@ declare namespace SecretsManagerV2 {
          *  certificates that are issued by this certificate authority.
          */
         crl_distribution_points_encoded?: boolean;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The distinguished name that identifies the entity that signed and issued the certificate. */
         issuer?: string;
@@ -3727,8 +3815,11 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
+        /** The requested value for the [`serialNumber`](https://datatracker.ietf.org/doc/html/rfc4519#section-2.31)
+         *  attribute that is in the certificate's distinguished name (DN).
+         *
+         *  **Note:** This field is not related to the `serial_number` field that is returned in the API response. The
+         *  `serial_number` field represents the certificate's randomly assigned serial number.
          */
         serial_number?: string;
     }
@@ -3754,7 +3845,9 @@ declare namespace SecretsManagerV2 {
          *  certificates that are issued by this certificate authority.
          */
         crl_distribution_points_encoded?: boolean;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The type of private key to generate. */
         key_type?: string;
@@ -3835,9 +3928,7 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
-         */
+        /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number?: string;
         /** The configuration data of your Private Certificate. */
         data?: PrivateCertificateCAData;
@@ -3864,7 +3955,9 @@ declare namespace SecretsManagerV2 {
          *  certificates that are issued by this certificate authority.
          */
         crl_distribution_points_encoded?: boolean;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The type of private key to generate. */
         key_type?: string;
@@ -4019,8 +4112,11 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
+        /** The requested value for the [`serialNumber`](https://datatracker.ietf.org/doc/html/rfc4519#section-2.31)
+         *  attribute that is in the certificate's distinguished name (DN).
+         *
+         *  **Note:** This field is not related to the `serial_number` field that is returned in the API response. The
+         *  `serial_number` field represents the certificate's randomly assigned serial number.
          */
         serial_number?: string;
     }
@@ -4172,9 +4268,7 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
-         */
+        /** This field is deprecated. You can ignore its value. */
         serial_number?: string;
         /** This field indicates whether to require a common name to create a private certificate.
          *
@@ -4353,9 +4447,7 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
-         */
+        /** This field is deprecated. You can ignore its value. */
         serial_number?: string;
         /** This field indicates whether to require a common name to create a private certificate.
          *
@@ -4534,9 +4626,7 @@ declare namespace SecretsManagerV2 {
         street_address?: string[];
         /** The postal code values to define in the subject field of the resulting certificate. */
         postal_code?: string[];
-        /** The serial number to assign to the generated certificate. To assign a random serial number, you can omit
-         *  this field.
-         */
+        /** This field is deprecated. You can ignore its value. */
         serial_number?: string;
         /** This field indicates whether to require a common name to create a private certificate.
          *
@@ -4620,7 +4710,9 @@ declare namespace SecretsManagerV2 {
         certificate_template: string;
         /** The Common Name (CN) represents the server name that is protected by the SSL certificate. */
         common_name: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** The distinguished name that identifies the entity that signed and issued the certificate. */
         issuer: string;
@@ -4634,7 +4726,9 @@ declare namespace SecretsManagerV2 {
          *  for secrets that can be auto-rotated and an existing rotation policy.
          */
         next_rotation_date?: string;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number: string;
@@ -4667,7 +4761,9 @@ declare namespace SecretsManagerV2 {
         labels?: string[];
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
     }
     /** PrivateCertificatePrototype. */
@@ -4734,7 +4830,9 @@ declare namespace SecretsManagerV2 {
          *  exceed the `max_ttl` that is defined in the associated certificate template.
          */
         ttl?: string;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
@@ -4773,7 +4871,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number: string;
@@ -4834,7 +4934,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number: string;
@@ -4909,7 +5011,9 @@ declare namespace SecretsManagerV2 {
         alt_names?: string[];
         /** The Common Name (CN) represents the server name protected by the SSL certificate. */
         common_name: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** Issuance information that is associated with your certificate. */
         issuance_info?: CertificateIssuanceInfo;
@@ -4920,14 +5024,16 @@ declare namespace SecretsManagerV2 {
          *
          *  The algorithm that you select determines the encryption algorithm (`RSA` or `ECDSA`) and key size to be used to
          *  generate keys and sign certificates. For longer living certificates, it is recommended to use longer keys to
-         *  provide more encryption protection. Allowed values:  `RSA2048`, `RSA4096`, `EC256`, and `EC384`.
+         *  provide more encryption protection. Allowed values:  `RSA2048`, `RSA4096`, `ECDSA256`, and `ECDSA384`.
          */
         key_algorithm: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number?: string;
         /** The date and time that the certificate validity period begins and ends. */
         validity?: CertificateValidity;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation: RotationPolicy;
         /** Indicates whether the issued certificate is bundled with intermediate certificates. */
         bundle_certs?: boolean;
@@ -5270,7 +5376,9 @@ declare namespace SecretsManagerV2 {
         alt_names?: string[];
         /** The Common Name (CN) represents the server name protected by the SSL certificate. */
         common_name: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** Issuance information that is associated with your certificate. */
         issuance_info?: CertificateIssuanceInfo;
@@ -5281,14 +5389,16 @@ declare namespace SecretsManagerV2 {
          *
          *  The algorithm that you select determines the encryption algorithm (`RSA` or `ECDSA`) and key size to be used to
          *  generate keys and sign certificates. For longer living certificates, it is recommended to use longer keys to
-         *  provide more encryption protection. Allowed values:  `RSA2048`, `RSA4096`, `EC256`, and `EC384`.
+         *  provide more encryption protection. Allowed values:  `RSA2048`, `RSA4096`, `ECDSA256`, and `ECDSA384`.
          */
         key_algorithm: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number?: string;
         /** The date and time that the certificate validity period begins and ends. */
         validity?: CertificateValidity;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation: RotationPolicy;
         /** Indicates whether the issued certificate is bundled with intermediate certificates. */
         bundle_certs?: boolean;
@@ -5319,7 +5429,9 @@ declare namespace SecretsManagerV2 {
         labels?: string[];
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
     }
     /** PublicCertificatePrototype. */
@@ -5359,24 +5471,20 @@ declare namespace SecretsManagerV2 {
          *
          *  The algorithm that you select determines the encryption algorithm (`RSA` or `ECDSA`) and key size to be used to
          *  generate keys and sign certificates. For longer living certificates, it is recommended to use longer keys to
-         *  provide more encryption protection. Allowed values:  `RSA2048`, `RSA4096`, `EC256`, and `EC384`.
+         *  provide more encryption protection. Allowed values:  `RSA2048`, `RSA4096`, `ECDSA256`, and `ECDSA384`.
          */
         key_algorithm?: string;
-        /** A human-readable unique name to assign to your configuration.
-         *
-         *  To protect your privacy, do not use personal data, such as your name or location, as an name for your secret.
-         */
+        /** The name of the certificate authority configuration. */
         ca: string;
-        /** A human-readable unique name to assign to your configuration.
-         *
-         *  To protect your privacy, do not use personal data, such as your name or location, as an name for your secret.
-         */
+        /** The name of the DNS provider configuration. */
         dns: string;
         /** This field indicates whether your issued certificate is bundled with intermediate certificates. Set to
          *  `false` for the certificate file to contain only the issued certificate.
          */
         bundle_certs?: boolean;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
@@ -5431,7 +5539,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number?: string;
@@ -5480,7 +5590,9 @@ declare namespace SecretsManagerV2 {
         version_custom_metadata?: JsonObject;
         /** A v4 UUID identifier. */
         secret_id: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The unique serial number that was assigned to a certificate by the issuing certificate authority. */
         serial_number?: string;
@@ -5545,9 +5657,13 @@ declare namespace SecretsManagerV2 {
         updated_at: string;
         /** The number of versions of your secret. */
         versions_total: number;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation: RotationPolicy;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The date that the secret is scheduled for automatic rotation.
          *
@@ -5609,9 +5725,13 @@ declare namespace SecretsManagerV2 {
         updated_at: string;
         /** The number of versions of your secret. */
         versions_total: number;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation: RotationPolicy;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The date that the secret is scheduled for automatic rotation.
          *
@@ -5642,9 +5762,13 @@ declare namespace SecretsManagerV2 {
         labels?: string[];
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
     }
     /** UsernamePasswordSecretPrototype. */
@@ -5677,13 +5801,17 @@ declare namespace SecretsManagerV2 {
         username: string;
         /** The password that is assigned to an `username_password` secret. */
         password: string;
-        /** The date when the secret material expires. The date format follows the `RFC 3339` format. */
+        /** The date when the secret material expires. The date format follows the `RFC 3339` format. Supported secret
+         *  types: Arbitrary, username_password.
+         */
         expiration_date?: string;
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
         /** The secret version metadata that a user can customize. */
         version_custom_metadata?: JsonObject;
-        /** This field indicates whether Secrets Manager rotates your secrets automatically. */
+        /** This field indicates whether Secrets Manager rotates your secrets automatically. Supported secret types:
+         *  username_password, private_cert, public_cert, iam_credentials.
+         */
         rotation?: RotationPolicy;
     }
     /** Your user credentials secret version. */
@@ -5759,7 +5887,7 @@ declare namespace SecretsManagerV2 {
     /** UsernamePasswordSecretVersionPrototype. */
     interface UsernamePasswordSecretVersionPrototype extends SecretVersionPrototype {
         /** The password that is assigned to an `username_password` secret. */
-        password: string;
+        password?: string;
         /** The secret metadata that a user can customize. */
         custom_metadata?: JsonObject;
         /** The secret version metadata that a user can customize. */