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

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Container Registry
  4. Resources
  5. container_repository

yandex_container_repository (Resource)

Written by
Yandex Cloud
Updated at October 2, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Nested Schema for timeouts
  • Import

A Repository resource. For more information, see Repository.

Example usageExample usage

//
// Create a new Container Registry and new Repository with it.
//
resource "yandex_container_registry" "my-registry" {
  name = "test-registry"
}

resource "yandex_container_repository" "my-repository" {
  name = "${yandex_container_registry.my-registry.id}/test-repository"
}

SchemaSchema

RequiredRequired

  • name (String) Name of the repository.
    The name is unique within the registry.

OptionalOptional

  • id (String) ID of the Repository resource to return.

To get the repository ID use a [RepositoryService.List] request.

  • repository_id (String) ID of the Repository resource to return.

To get the repository ID use a [RepositoryService.List] request.

  • timeouts (Block, Optional) (see below for nested schema)

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

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_container_repository.<resource Name> <repository_id>
terraform import yandex_container_repository.my-repository crps9**********k9psn

Was the article helpful?

Previous
container_registry_ip_permission
Next
container_repository_iam_binding
© 2025 Direct Cursus Technology L.L.C.