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
          • container_registry
          • container_registry_ip_permission
          • container_repository
          • container_repository_lifecycle_policy

In this article:

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

yandex_container_registry_ip_permission (Data Source)

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

Get information about a Yandex Container Registry IP Permission. For more information, see the official documentation.

Warning

Either registry_id or registry_name must be specified.

Example usageExample usage

//
// Get information about existing IP Permission of specific Container Registry.
//
data "yandex_container_registry_ip_permission" "my_ip_permission_by_id" {
  registry_id = yandex_container_registry.my_registry.id
}

SchemaSchema

OptionalOptional

  • registry_id (String) The ID of the registry that ip restrictions applied to.
  • registry_name (String) The Name of specific Container Registry.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • id (String) The ID of this resource.
  • pull (Set of String) List of configured CIDRs, from which pull is allowed.
  • push (Set of String) List of configured CIDRs, from which push is allowed.

Nested Schema for Nested Schema for timeouts

Optional:

  • default (String)

Was the article helpful?

Previous
container_registry
Next
container_repository
© 2025 Direct Cursus Technology L.L.C.