yandex_container_repository_lifecycle_policy (Resource)

Creates a new container repository lifecycle policy. For more information, see the official documentation.

Example usageExample usage

//
// Create new Container Repository and Container Repository Lifecycle Policy for 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"
}

resource "yandex_container_repository_lifecycle_policy" "my_lifecycle_policy" {
  name          = "test-lifecycle-policy-name"
  status        = "active"
  repository_id = yandex_container_repository.my_repository.id

  rule {
    description  = "my description"
    untagged     = true
    tag_regexp   = ".*"
    retained_top = 1
  }
}

SchemaSchema

RequiredRequired

• repository_id (String) The ID of the repository that the resource belongs to.
• status (String) The status of lifecycle policy. Must be active or disabled.

OptionalOptional

• description (String) The resource description.
• name (String) The resource name.
• rule (Block List) Repository rules. (see below for nested schema)
• timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

• created_at (String) The creation timestamp of the resource.
• id (String) The ID of this resource.

Nested Schema for Nested Schema for rule

Optional:

• description (String) Description of the lifecycle policy.
• expire_period (String) The period of time that must pass after creating a image for it to suit the automatic deletion criteria. It must be a multiple of 24 hours.
• retained_top (Number) The number of images to be retained even if the expire_period already expired.
• tag_regexp (String) Tag to specify a filter as a regular expression. For example .* - all images with tags.
• untagged (Boolean) If enabled, rules apply to untagged Docker images.

Nested Schema for Nested Schema for timeouts

Optional:

• default (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_lifecycle_policy.<resource Name> <resource Id>
terraform import yandex_container_repository_lifecycle_policy.my_lifecycle_policy ...