Data Source: oci_devops_repository

This data source provides details about a specific Repository resource in Oracle Cloud Infrastructure Devops service.

Retrieves a repository by identifier.

Example Usage

data "oci_devops_repository" "test_repository" {
	#Required
	repository_id = oci_devops_repository.test_repository.id

	#Optional
	fields = var.repository_fields
}

Argument Reference

The following arguments are supported:

• fields - (Optional) Fields parameter can contain multiple flags useful in deciding the API functionality.
• repository_id - (Required) Unique repository identifier.

Attributes Reference

The following attributes are exported:

• branch_count - The count of the branches present in the repository.
• commit_count - The count of the commits present in the repository.
• compartment_id - The OCID of the repository’s compartment.
• default_branch - The default branch of the repository.
• defined_tags - Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {"foo-namespace.bar-key": "value"}
• description - Details of the repository. Avoid entering confidential information.
• freeform_tags - Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. See Resource Tags. Example: {"bar-key": "value"}
• http_url - HTTP URL that you use to git clone, pull and push.
• id - The OCID of the repository. This value is unique and immutable.
• lifecyle_details - A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
• mirror_repository_config - Configuration information for mirroring the repository.
  • connector_id - Upstream git repository connection identifier.
  • repository_url - URL of external repository you want to mirror.
  • trigger_schedule - Specifies a trigger schedule. Timing information for when to initiate automated syncs.
    • custom_schedule - Valid if type is CUSTOM. Following RFC 5545 recurrence rules, we can specify starting time, occurrence frequency, and interval size. Example for frequency could be DAILY/WEEKLY/HOURLY or any RFC 5545 supported frequency, which is followed by start time of this window. You can control the start time with BYHOUR, BYMINUTE and BYSECONDS. It is followed by the interval size.
    • schedule_type - Different types of trigger schedule: NONE - No automated synchronization schedule. DEFAULT - Trigger schedule is every 30 minutes. CUSTOM - Custom triggering schedule.
• name - Name of the repository. Should be unique within the project. This value is mutable.
• namespace - Tenancy unique namespace.
• parent_repository_id - The OCID of the parent repository.
• project_id - The OCID of the DevOps project containing the repository.
• project_name - Unique project name in a namespace.
• repository_type - Type of repository: MIRRORED - Repository created by mirroring an existing repository. HOSTED - Repository created and hosted using Oracle Cloud Infrastructure DevOps code repository. FORKED - Repository created by forking an existing repository.
• size_in_bytes - The size of the repository in bytes.
• ssh_url - SSH URL that you use to git clone, pull and push.
• state - The current state of the repository.
• system_tags - Usage of system tag keys. These predefined keys are scoped to namespaces. See Resource Tags. Example: {"orcl-cloud.free-tier-retained": "true"}
• time_created - The time the repository was created. Format defined by RFC3339.
• time_updated - The time the repository was updated. Format defined by RFC3339.
• trigger_build_events - Trigger build events supported for this repository: PUSH - Build is triggered when a push event occurs. PULL_REQUEST_CREATED - Build is triggered when a pull request is created in the repository. PULL_REQUEST_UPDATED - Build is triggered when a push is made to a branch with an open pull request. COMMIT_UPDATES - Build is triggered when new commits are mirrored into a repository.