oracle.oci.oci_devops_repository_ref – Manage a RepositoryRef resource in Oracle Cloud Infrastructure

Note

This plugin is part of the oracle.oci collection (version 4.11.0).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install oracle.oci.

To use it in a playbook, specify: oracle.oci.oci_devops_repository_ref.

New in version 2.9.0: of oracle.oci

Synopsis

  • This module allows the user to update and delete a RepositoryRef resource in Oracle Cloud Infrastructure

Requirements

The below requirements are needed on the host that executes this module.

Parameters

Parameter Choices/Defaults Comments
api_user
string
The OCID of the user, on whose behalf, OCI APIs are invoked. If not set, then the value of the OCI_USER_ID environment variable, if any, is used. This option is required if the user is not specified through a configuration file (See config_file_location). To get the user's OCID, please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm.
api_user_fingerprint
string
Fingerprint for the key pair being used. If not set, then the value of the OCI_USER_FINGERPRINT environment variable, if any, is used. This option is required if the key fingerprint is not specified through a configuration file (See config_file_location). To get the key pair's fingerprint value please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm.
api_user_key_file
string
Full path and filename of the private key (in PEM format). If not set, then the value of the OCI_USER_KEY_FILE variable, if any, is used. This option is required if the private key is not specified through a configuration file (See config_file_location). If the key is encrypted with a pass-phrase, the api_user_key_pass_phrase option must also be provided.
api_user_key_pass_phrase
string
Passphrase used by the key referenced in api_user_key_file, if it is encrypted. If not set, then the value of the OCI_USER_KEY_PASS_PHRASE variable, if any, is used. This option is required if the key passphrase is not specified through a configuration file (See config_file_location).
auth_purpose
string
    Choices:
  • service_principal
The auth purpose which can be used in conjunction with 'auth_type=instance_principal'. The default auth_purpose for instance_principal is None.
auth_type
string
    Choices:
  • api_key ←
  • instance_principal
  • instance_obo_user
  • resource_principal
The type of authentication to use for making API requests. By default auth_type="api_key" based authentication is performed and the API key (see api_user_key_file) in your config file will be used. If this 'auth_type' module option is not specified, the value of the OCI_ANSIBLE_AUTH_TYPE, if any, is used. Use auth_type="instance_principal" to use instance principal based authentication when running ansible playbooks within an OCI compute instance.
cert_bundle
string
The full path to a CA certificate bundle to be used for SSL verification. This will override the default CA certificate bundle. If not set, then the value of the OCI_ANSIBLE_CERT_BUNDLE variable, if any, is used.
commit_id
string
Commit ID pointed to by the new branch.
This parameter is updatable.
Required when ref_type is 'BRANCH'
config_file_location
string
Path to configuration file. If not set then the value of the OCI_CONFIG_FILE environment variable, if any, is used. Otherwise, defaults to ~/.oci/config.
config_profile_name
string
The profile to load from the config file referenced by config_file_location. If not set, then the value of the OCI_CONFIG_PROFILE environment variable, if any, is used. Otherwise, defaults to the "DEFAULT" profile in config_file_location.
object_id
string
SHA-1 hash value of the object pointed to by the tag.
This parameter is updatable.
Required when ref_type is 'TAG'
ref_name
string / required
A filter to return only resources that match the given reference name.
ref_type
string
    Choices:
  • TAG
  • BRANCH
The type of reference (BRANCH or TAG).
Required for update using state=present with ref_name present.
region
string
The Oracle Cloud Infrastructure region to use for all OCI API requests. If not set, then the value of the OCI_REGION variable, if any, is used. This option is required if the region is not specified through a configuration file (See config_file_location). Please refer to https://docs.us-phoenix-1.oraclecloud.com/Content/General/Concepts/regions.htm for more information on OCI regions.
repository_id
string / required
Unique repository identifier.
state
string
    Choices:
  • present ←
  • absent
The state of the RepositoryRef.
Use state=present to update an existing a RepositoryRef.
Use state=absent to delete a RepositoryRef.
tenancy
string
OCID of your tenancy. If not set, then the value of the OCI_TENANCY variable, if any, is used. This option is required if the tenancy OCID is not specified through a configuration file (See config_file_location). To get the tenancy OCID, please refer https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm
wait
boolean
    Choices:
  • no
  • yes ←
Whether to wait for create or delete operation to complete.
wait_timeout
integer
Time, in seconds, to wait when wait=yes. Defaults to 1200 for most of the services but some services might have a longer wait timeout.

Examples

- name: Update repository_ref with ref_type = TAG
  oci_devops_repository_ref:
    # required
    object_id: "ocid1.object.oc1..xxxxxxEXAMPLExxxxxx"
    ref_type: TAG

- name: Update repository_ref with ref_type = BRANCH
  oci_devops_repository_ref:
    # required
    ref_type: BRANCH
    commit_id: "ocid1.commit.oc1..xxxxxxEXAMPLExxxxxx"

- name: Delete repository_ref
  oci_devops_repository_ref:
    # required
    repository_id: "ocid1.repository.oc1..xxxxxxEXAMPLExxxxxx"
    ref_name: ref_name_example
    state: absent

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key Returned Description
repository_ref
complex
on success
Details of the RepositoryRef resource acted upon by the current operation

Sample:
{'commit_id': 'ocid1.commit.oc1..xxxxxxEXAMPLExxxxxx', 'defined_tags': {'Operations': {'CostCenter': 'US'}}, 'freeform_tags': {'Department': 'Finance'}, 'full_ref_name': 'full_ref_name_example', 'object_id': 'ocid1.object.oc1..xxxxxxEXAMPLExxxxxx', 'ref_name': 'ref_name_example', 'ref_type': 'BRANCH', 'repository_id': 'ocid1.repository.oc1..xxxxxxEXAMPLExxxxxx'}
 
commit_id
string
on success
Commit ID pointed to by the new branch.

Sample:
ocid1.commit.oc1..xxxxxxEXAMPLExxxxxx
 
defined_tags
dictionary
on success
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: `{"foo-namespace": {"bar-key": "value"}}`

Sample:
{'Operations': {'CostCenter': 'US'}}
 
freeform_tags
dictionary
on success
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"}`

Sample:
{'Department': 'Finance'}
 
full_ref_name
string
on success
Unique full reference name inside a repository.

Sample:
full_ref_name_example
 
object_id
string
on success
SHA-1 hash value of the object pointed to by the tag.

Sample:
ocid1.object.oc1..xxxxxxEXAMPLExxxxxx
 
ref_name
string
on success
Unique reference name inside a repository.

Sample:
ref_name_example
 
ref_type
string
on success
The type of reference (BRANCH or TAG).

Sample:
BRANCH
 
repository_id
string
on success
The OCID of the repository containing the reference.

Sample:
ocid1.repository.oc1..xxxxxxEXAMPLExxxxxx


Authors

  • Oracle (@oracle)