Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Популярные
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ИИ для бизнеса
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Облако для интеграторов
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Контент-программа
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ООО «Яндекс.Облако»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • Обзор
    • История изменений (англ.)
          • lockbox_secret
          • lockbox_secret_iam_binding
          • lockbox_secret_iam_member
          • lockbox_secret_version
          • lockbox_secret_version_hashed

В этой статье:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Lockbox (Secret Management)
  4. Resources
  5. lockbox_secret_version_hashed

yandex_lockbox_secret_version_hashed (Resource)

Статья создана
Yandex Cloud
Обновлена 11 сентября 2025 г.
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for timeouts
  • Import

Yandex Cloud Lockbox secret version resource (with values hashed in state). For more information, see the official documentation.

~> The <NUMBER> can range from 1 to 10. If you only need one entry, use key_1/text_value_1. If you need a second entry, use key_2/text_value_2, and so on.

Example usageExample usage

//
// Create a new Lockbox Secret Hashed Version.
//
resource "yandex_lockbox_secret" "my_secret" {
  name = "test secret"
}

resource "yandex_lockbox_secret_version_hashed" "my_version" {
  secret_id = yandex_lockbox_secret.my_secret.id
  key_1     = "key1"
  // in Terraform state, these values will be stored in hash format
  text_value_1 = "sensitive value 1"
  key_2        = "k2"
  text_value_2 = "sensitive value 2"
  // etc. (up to 10 entries)
}

SchemaSchema

RequiredRequired

  • secret_id (String) The Yandex Cloud Lockbox secret ID where to add the version.

OptionalOptional

  • description (String) The Yandex Cloud Lockbox secret version description.
  • key_1 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_10 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_2 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_3 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_4 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_5 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_6 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_7 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_8 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • key_9 (String) Each of the entry keys in the Yandex Cloud Lockbox secret version.
  • text_value_1 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_10 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_2 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_3 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_4 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_5 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_6 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_7 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_8 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • text_value_9 (String, Sensitive) Each of the entry values in the Yandex Cloud Lockbox secret version.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • id (String) The ID of this resource.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.

ImportImport

Важно

Import for this resource is not implemented yet.

Была ли статья полезна?

Предыдущая
lockbox_secret_version
Следующая
kubernetes_marketplace_helm_release
Проект Яндекса
© 2025 ООО «Яндекс.Облако»