/** * Vault Secret Management API * Use the Secret Management API to manage secrets and secret versions. For more information, see [Managing Secrets](https://docs.oracle.com/iaas/Content/KeyManagement/Tasks/managingsecrets.htm). * OpenAPI spec version: 20180608 * * * NOTE: This class is auto generated by OracleSDKGenerator. * Do not edit the class manually. * * Copyright (c) 2020, 2026, Oracle and/or its affiliates. All rights reserved. * This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license. */ /** * The content of the secret and metadata to help identify it. */ export interface SecretContentDetails { /** * Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods. */ "name"?: string; /** * The rotation state of the secret content. The default is {@code CURRENT}, meaning that the secret is currently in use. A secret version * that you mark as {@code PENDING} is staged and available for use, but you don't yet want to rotate it into current, active use. For example, * you might create or update a secret and mark its rotation state as {@code PENDING} if you haven't yet updated the secret on the target system. * When creating a secret, only the value {@code CURRENT} is applicable, although the value {@code LATEST} is also automatically applied. When updating * a secret, you can specify a version's rotation state as either {@code CURRENT} or {@code PENDING}. * */ "stage"?: SecretContentDetails.Stage; "contentType": string; } export declare namespace SecretContentDetails { enum Stage { Current = "CURRENT", Pending = "PENDING" } function getJsonObj(obj: SecretContentDetails): object; function getDeserializedJsonObj(obj: SecretContentDetails): object; }