Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • cloudregistry_registry
          • cloudregistry_registry_ip_permission

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  1. Terraform reference
  2. Resources
  3. Cloud Registry
  4. Data Sources
  5. cloudregistry_registry_ip_permission

yandex_cloudregistry_registry_ip_permission (Data Source)

Written by
Yandex Cloud
Updated at September 18, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts

Creates a new Cloud Registry IP Permission. For more information, see the official documentation

Example usageExample usage

//
// Get information about existing IP Permission of specific Cloud Registry.
//
data "yandex_cloudregistry_registry_ip_permission" "my_ip_permission_by_registry_id" {
  registry_id = yandex_cloudregistry_registry.my_registry.id
}

SchemaSchema

OptionalOptional

  • pull (Set of String) List of configured CIDRs from which pull operations are allowed.
  • push (Set of String) List of configured CIDRs from which push operations are allowed.
  • registry_id (String) The ID of the registry that IP restrictions are applied to.
  • registry_name (String) The name of the registry that IP restrictions are applied to.
  • timeouts (Attributes) (see below for nested schema)

Read-OnlyRead-Only

  • id (String) The ID of IP permission.

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).

Was the article helpful?

Previous
cloudregistry_registry
Next
cloudregistry_registry
© 2025 Direct Cursus Technology L.L.C.