oracle.oci.oci_functions_function_facts – Fetches details about one or multiple Function resources in Oracle Cloud Infrastructure

Note

This plugin is part of the oracle.oci collection (version 5.3.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_functions_function_facts.

New in version 2.9.0: of oracle.oci

Synopsis

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

  • Lists functions for an application.

  • If function_id is specified, the details of a single Function 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).
application_id
string
The OCID of the application to which this function belongs.
Required to list multiple functions.
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
  • security_token
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.
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 functions with display names that match the display name string. Matching is exact.

aliases: name
function_id
string
The OCID of this function.
Required to get a specific function.

aliases: id
lifecycle_state
string
    Choices:
  • CREATING
  • ACTIVE
  • INACTIVE
  • UPDATING
  • DELETING
  • DELETED
  • FAILED
A filter to return only functions that match the lifecycle state in this parameter. Example: `Creating`
realm_specific_endpoint_template_enabled
boolean
    Choices:
  • no
  • yes
Enable/Disable realm specific endpoint template for service client. By Default, realm specific endpoint template is disabled. If not set, then the value of the OCI_REALM_SPECIFIC_SERVICE_ENDPOINT_TEMPLATE_ENABLED variable, if any, is used.
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.
sort_by
string
    Choices:
  • timeCreated
  • id
  • displayName
Specifies the attribute with which to sort the rules.
Default: `displayName`
* **timeCreated:** Sorts by timeCreated. * **displayName:** Sorts by displayName. * **id:** Sorts by id.
sort_order
string
    Choices:
  • ASC
  • DESC
Specifies sort order.
* **ASC:** Ascending sort order. * **DESC:** Descending sort order.
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 function
  oci_functions_function_facts:
    # required
    function_id: "ocid1.function.oc1..xxxxxxEXAMPLExxxxxx"

- name: List functions
  oci_functions_function_facts:
    # required
    application_id: "ocid1.application.oc1..xxxxxxEXAMPLExxxxxx"

    # optional
    lifecycle_state: CREATING
    display_name: display_name_example
    sort_order: ASC
    sort_by: timeCreated

Return Values

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

Key Returned Description
functions
complex
on success
List of Function resources

Sample:
[{'application_id': 'ocid1.application.oc1..xxxxxxEXAMPLExxxxxx', 'compartment_id': 'ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx', 'config': {}, 'defined_tags': {'Operations': {'CostCenter': 'US'}}, 'display_name': 'display_name_example', 'freeform_tags': {'Department': 'Finance'}, 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'image': 'image_example', 'image_digest': 'image_digest_example', 'invoke_endpoint': 'invoke_endpoint_example', 'lifecycle_state': 'CREATING', 'memory_in_mbs': 56, 'provisioned_concurrency_config': {'count': 56, 'strategy': 'CONSTANT'}, 'shape': 'GENERIC_X86', 'source_details': {'pbf_listing_id': 'ocid1.pbflisting.oc1..xxxxxxEXAMPLExxxxxx', 'source_type': 'PRE_BUILT_FUNCTIONS'}, 'time_created': '2013-10-20T19:20:30+01:00', 'time_updated': '2013-10-20T19:20:30+01:00', 'timeout_in_seconds': 56, 'trace_config': {'is_enabled': True}}]
 
application_id
string
on success
The OCID of the application the function belongs to.

Sample:
ocid1.application.oc1..xxxxxxEXAMPLExxxxxx
 
compartment_id
string
on success
The OCID of the compartment that contains the function.

Sample:
ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
 
config
dictionary
on success
Function configuration. Overrides application configuration. Keys must be ASCII strings consisting solely of letters, digits, and the '_' (underscore) character, and must not begin with a digit. Values should be limited to printable unicode characters.
Example: `{"MY_FUNCTION_CONFIG": "ConfVal"}`
The maximum size for all configuration keys and values is limited to 4KB. This is measured as the sum of octets necessary to represent each key and value in UTF-8.
Returned for get operation
 
defined_tags
dictionary
on success
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: `{"Operations": {"CostCenter": "42"}}`

Sample:
{'Operations': {'CostCenter': 'US'}}
 
display_name
string
on success
The display name of the function. The display name is unique within the application containing the function.

Sample:
display_name_example
 
freeform_tags
dictionary
on success
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: `{"Department": "Finance"}`

Sample:
{'Department': 'Finance'}
 
id
string
on success
The OCID of the function.

Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
 
image
string
on success
The qualified name of the Docker image to use in the function, including the image tag. The image should be in the OCI Registry that is in the same region as the function itself. Example: `phx.ocir.io/ten/functions/function:0.0.1`

Sample:
image_example
 
image_digest
string
on success
The image digest for the version of the image that will be pulled when invoking this function. If no value is specified, the digest currently associated with the image in the OCI Registry will be used. Example: `sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7`

Sample:
image_digest_example
 
invoke_endpoint
string
on success
The base https invoke URL to set on a client in order to invoke a function. This URL will never change over the lifetime of the function and can be cached.

Sample:
invoke_endpoint_example
 
lifecycle_state
string
on success
The current state of the function.

Sample:
CREATING
 
memory_in_mbs
integer
on success
Maximum usable memory for the function (MiB).

Sample:
56
 
provisioned_concurrency_config
complex
on success

   
count
integer
on success
Configuration specifying a constant amount of provisioned concurrency.

Sample:
56
   
strategy
string
on success
The strategy for provisioned concurrency to be used.

Sample:
CONSTANT
 
shape
string
on success
The processor shape (`GENERIC_X86`/`GENERIC_ARM`) on which to run functions in the application, extracted from the image manifest.

Sample:
GENERIC_X86
 
source_details
complex
on success

   
pbf_listing_id
string
on success
The OCID of the PbfListing this function is sourced from.

Sample:
ocid1.pbflisting.oc1..xxxxxxEXAMPLExxxxxx
   
source_type
string
on success
Type of the Function Source. Possible values: PBF.

Sample:
PRE_BUILT_FUNCTIONS
 
time_created
string
on success
The time the function was created, expressed in RFC 3339 timestamp format.
Example: `2018-09-12T22:47:12.613Z`

Sample:
2013-10-20T19:20:30+01:00
 
time_updated
string
on success
The time the function was updated, expressed in RFC 3339 timestamp format.
Example: `2018-09-12T22:47:12.613Z`

Sample:
2013-10-20T19:20:30+01:00
 
timeout_in_seconds
integer
on success
Timeout for executions of the function. Value in seconds.

Sample:
56
 
trace_config
complex
on success

   
is_enabled
boolean
on success
Define if tracing is enabled for the resource.

Sample:
True


Authors

  • Oracle (@oracle)