oracle.oci.oci_artifacts_container_image_signature_facts – Fetches details about one or multiple ContainerImageSignature resources 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_artifacts_container_image_signature_facts.

New in version 2.9.0: of oracle.oci

Synopsis

  • Fetches details about one or multiple ContainerImageSignature resources in Oracle Cloud Infrastructure

  • List container image signatures in an image.

  • If image_signature_id is specified, the details of a single ContainerImageSignature will be returned.

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.
compartment_id
string
The OCID of the compartment.
Required to list multiple container_image_signatures.
compartment_id_in_subtree
boolean
    Choices:
  • no
  • yes
When set to true, the hierarchy of compartments is traversed and all compartments and subcompartments in the tenancy are inspected depending on the the setting of `accessLevel`. Default is false. Can only be set to true when calling the API on the tenancy (root compartment).
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.
display_name
string
A filter to return only resources that match the given display name exactly.

aliases: name
image_digest
string
The digest of the container image.
Example: `sha256:e7d38b3517548a1c71e41bffe9c8ae6d6d29546ce46bf62159837aad072c90aa`
image_id
string
A filter to return a container image summary only for the specified container image OCID.
image_signature_id
string
The OCID of the container image signature.
Example: `ocid1.containersignature.oc1..exampleuniqueID`
Required to get a specific container_image_signature.

aliases: id
kms_key_id
string
The OCID of the kmsKeyVersionId used to sign the container image.
Example: `ocid1.keyversion.oc1..exampleuniqueID`
kms_key_version_id
string
The OCID of the kmsKeyVersionId used to sign the container image.
Example: `ocid1.keyversion.oc1..exampleuniqueID`
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
A filter to return container images only for the specified container repository OCID.
repository_name
string
A filter to return container images or container image signatures that match the repository name.
Example: `foo` or `foo*`
signing_algorithm
string
    Choices:
  • SHA_224_RSA_PKCS_PSS
  • SHA_256_RSA_PKCS_PSS
  • SHA_384_RSA_PKCS_PSS
  • SHA_512_RSA_PKCS_PSS
The algorithm to be used for signing. These are the only supported signing algorithms for container images.
sort_by
string
    Choices:
  • TIMECREATED
  • DISPLAYNAME
The field to sort by. You can provide one sort order (`sortOrder`). Default order for TIMECREATED is descending. Default order for DISPLAYNAME is ascending. The DISPLAYNAME sort order is case sensitive.
**Note:** In general, some "List" operations (for example, `ListInstances`) let you optionally filter by availability domain if the scope of the resource type is within a single availability domain. If you call one of these "List" operations without specifying an availability domain, the resources are grouped by availability domain, then sorted.
sort_order
string
    Choices:
  • ASC
  • DESC
The sort order to use, either ascending (`ASC`) or descending (`DESC`). The DISPLAYNAME sort order is case sensitive.
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

Examples

- name: Get a specific container_image_signature
  oci_artifacts_container_image_signature_facts:
    # required
    image_signature_id: "ocid1.imagesignature.oc1..xxxxxxEXAMPLExxxxxx"

- name: List container_image_signatures
  oci_artifacts_container_image_signature_facts:
    # required
    compartment_id: "ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx"

    # optional
    compartment_id_in_subtree: true
    image_id: "ocid1.image.oc1..xxxxxxEXAMPLExxxxxx"
    repository_id: "ocid1.repository.oc1..xxxxxxEXAMPLExxxxxx"
    repository_name: repository_name_example
    image_digest: image_digest_example
    display_name: display_name_example
    kms_key_id: "ocid1.kmskey.oc1..xxxxxxEXAMPLExxxxxx"
    kms_key_version_id: "ocid1.kmskeyversion.oc1..xxxxxxEXAMPLExxxxxx"
    signing_algorithm: SHA_224_RSA_PKCS_PSS
    sort_by: TIMECREATED
    sort_order: ASC

Return Values

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

Key Returned Description
container_image_signatures
complex
on success
List of ContainerImageSignature resources

Sample:
[{'compartment_id': 'ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx', 'created_by': 'created_by_example', 'display_name': 'display_name_example', 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'image_id': 'ocid1.image.oc1..xxxxxxEXAMPLExxxxxx', 'kms_key_id': 'ocid1.kmskey.oc1..xxxxxxEXAMPLExxxxxx', 'kms_key_version_id': 'ocid1.kmskeyversion.oc1..xxxxxxEXAMPLExxxxxx', 'message': 'message_example', 'signature': 'signature_example', 'signing_algorithm': 'SHA_224_RSA_PKCS_PSS', 'time_created': '2013-10-20T19:20:30+01:00'}]
 
compartment_id
string
on success
The OCID of the compartment in which the container repository exists.

Sample:
ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
 
created_by
string
on success
The id of the user or principal that created the resource.
Returned for get operation

Sample:
created_by_example
 
display_name
string
on success
The last 10 characters of the kmsKeyId, the last 10 characters of the kmsKeyVersionId, the signingAlgorithm, and the last 10 characters of the signatureId.
Example: `wrmz22sixa::qdwyc2ptun::SHA_256_RSA_PKCS_PSS::2vwmobasva`

Sample:
display_name_example
 
id
string
on success
The OCID of the container image signature.
Example: `ocid1.containerimagesignature.oc1..exampleuniqueID`

Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
 
image_id
string
on success
The OCID of the container image.
Example: `ocid1.containerimage.oc1..exampleuniqueID`

Sample:
ocid1.image.oc1..xxxxxxEXAMPLExxxxxx
 
kms_key_id
string
on success
The OCID of the kmsKeyId used to sign the container image.
Example: `ocid1.key.oc1..exampleuniqueID`

Sample:
ocid1.kmskey.oc1..xxxxxxEXAMPLExxxxxx
 
kms_key_version_id
string
on success
The OCID of the kmsKeyVersionId used to sign the container image.
Example: `ocid1.keyversion.oc1..exampleuniqueID`

Sample:
ocid1.kmskeyversion.oc1..xxxxxxEXAMPLExxxxxx
 
message
string
on success
The base64 encoded signature payload that was signed.

Sample:
message_example
 
signature
string
on success
The signature of the message field using the kmsKeyId, the kmsKeyVersionId, and the signingAlgorithm.

Sample:
signature_example
 
signing_algorithm
string
on success
The algorithm to be used for signing. These are the only supported signing algorithms for container images.

Sample:
SHA_224_RSA_PKCS_PSS
 
time_created
string
on success
An RFC 3339 timestamp indicating when the image was created.

Sample:
2013-10-20T19:20:30+01:00


Authors

  • Oracle (@oracle)