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

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

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Cloud Organization
  4. Data Sources
  5. organizationmanager_idp_user

yandex_organizationmanager_idp_user (Data Source)

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

A user in the Identity Provider system.

Users are created within a userpool and can authenticate to access cloud resources.
Each user has a unique identifier, credentials, and profile information.

Example usageExample usage

//
// Get information about existing OrganizationManager Idp User.
//
data "yandex_organizationmanager_idp_user" "user" {
  user_id = "some_user_id"
}

output "my_user.username" {
  value = data.yandex_organizationmanager_idp_user.user.username
}

output "my_user.full_name" {
  value = data.yandex_organizationmanager_idp_user.user.full_name
}

SchemaSchema

OptionalOptional

  • id (String) ID of the user to return.
  • timeouts (Attributes) (see below for nested schema)
  • user_id (String) ID of the user to return.

Read-OnlyRead-Only

  • created_at (String) Timestamp when the user was created.
  • email (String) User's email address.
  • external_id (String) External identifier for federation with external identity systems.
    This ID can be used to link this user with an account in an external system.
  • family_name (String) User's last name.
    Part of the user's profile information.
  • full_name (String) User's full name (display name).
    This is typically shown in the UI and used for identification purposes.
  • given_name (String) User's first name.
    Part of the user's profile information.
  • phone_number (String) User's phone number.
  • status (String) Current status of the user.
    Determines whether the user can authenticate and access the system.
  • updated_at (String) Timestamp when the user was last updated.
  • username (String) Username used for authentication.
    Usually in the format of an email address.
  • userpool_id (String) ID of the userpool this user belongs to.
    To get the userpool ID, make a [UserpoolService.List] request.

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.
  • update (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).

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

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