oracle.oci.oci_optimizer_resource_action_facts – Fetches details about one or multiple ResourceAction 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_optimizer_resource_action_facts.

New in version 2.9.0: of oracle.oci

Synopsis

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

  • Lists the Cloud Advisor resource actions that are supported.

  • If resource_action_id is specified, the details of a single ResourceAction 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.
child_tenancy_ids
list / elements=string
A list of child tenancies for which the respective data will be returned. Please note that the parent tenancy id can also be included in this list. For example, if there is a parent P with two children A and B, to return results of only parent P and child A, this list should be populated with tenancy id of parent P and child A.
If this list contains a tenancy id that isn't part of the organization of parent P, the request will fail. That is, let's say there is an organization with parent P with children A and B, and also one other tenant T that isn't part of the organization. If T is included in the list of childTenancyIds, the request will fail.
It is important to note that if you are setting the includeOrganization parameter value as true and also populating the childTenancyIds parameter with a list of child tenancies, the request will fail. The childTenancyIds and includeOrganization should be used exclusively.
When using this parameter, please make sure to set the compartmentId with the parent tenancy ID.
compartment_id
string
The OCID of the compartment.
Required to list multiple resource_actions.
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 returned depending on the the setting of `accessLevel`.
Can only be set to true when performing ListCompartments on the tenancy (root compartment).
Required to list multiple resource_actions.
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.
include_organization
boolean
    Choices:
  • no
  • yes
When set to true, the data for all child tenancies including the parent is returned. That is, if there is an organization with parent P and children A and B, to return the data for the parent P, child A and child B, this parameter value should be set to true.
Please note that this parameter shouldn't be used along with childTenancyIds parameter. If you would like to get results specifically for parent P and only child A, use the childTenancyIds parameter and populate the list with tenancy id of P and A.
When using this parameter, please make sure to set the compartmentId with the parent tenancy ID.
lifecycle_state
string
    Choices:
  • ACTIVE
  • FAILED
  • INACTIVE
  • ATTACHING
  • DETACHING
  • DELETING
  • DELETED
  • UPDATING
  • CREATING
A filter that returns results that match the lifecycle state specified.
name
string
Optional. A filter that returns results that match the name specified.
recommendation_id
string
The unique OCID associated with the recommendation.
recommendation_name
string
Optional. A filter that returns results that match the recommendation name specified.
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.
resource_action_id
string
The unique OCID associated with the resource action.
Required to get a specific resource_action.

aliases: id
resource_type
string
Optional. A filter that returns results that match the resource type specified.
sort_by
string
    Choices:
  • NAME
  • TIMECREATED
The field to sort by. You can provide one sort order (`sortOrder`). Default order for TIMECREATED is descending. Default order for NAME is ascending. The NAME sort order is case sensitive.
sort_order
string
    Choices:
  • ASC
  • DESC
The sort order to use, either ascending (`ASC`) or descending (`DESC`).
status
string
    Choices:
  • PENDING
  • DISMISSED
  • POSTPONED
  • IMPLEMENTED
A filter that returns recommendations that match the status specified.
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 resource_action
  oci_optimizer_resource_action_facts:
    # required
    resource_action_id: "ocid1.resourceaction.oc1..xxxxxxEXAMPLExxxxxx"

- name: List resource_actions
  oci_optimizer_resource_action_facts:
    # required
    compartment_id: "ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx"
    compartment_id_in_subtree: true

    # optional
    recommendation_id: "ocid1.recommendation.oc1..xxxxxxEXAMPLExxxxxx"
    recommendation_name: recommendation_name_example
    child_tenancy_ids: [ "child_tenancy_ids_example" ]
    include_organization: true
    name: name_example
    resource_type: resource_type_example
    sort_order: ASC
    sort_by: NAME
    lifecycle_state: ACTIVE
    status: PENDING

Return Values

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

Key Returned Description
resource_actions
complex
on success
List of ResourceAction resources

Sample:
[{'action': {'description': 'description_example', 'type': 'KB_ARTICLE', 'url': 'url_example'}, 'category_id': 'ocid1.category.oc1..xxxxxxEXAMPLExxxxxx', 'compartment_id': 'ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx', 'compartment_name': 'compartment_name_example', 'estimated_cost_saving': 1.2, 'extended_metadata': {}, 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'lifecycle_state': 'ACTIVE', 'metadata': {}, 'name': 'name_example', 'recommendation_id': 'ocid1.recommendation.oc1..xxxxxxEXAMPLExxxxxx', 'resource_id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'resource_type': 'resource_type_example', 'status': 'PENDING', 'time_created': '2013-10-20T19:20:30+01:00', 'time_status_begin': '2013-10-20T19:20:30+01:00', 'time_status_end': '2013-10-20T19:20:30+01:00', 'time_updated': '2013-10-20T19:20:30+01:00'}]
 
action
complex
on success

   
description
string
on success
Text describing the recommended action.

Sample:
description_example
   
type
string
on success
The status of the resource action.

Sample:
KB_ARTICLE
   
url
string
on success
The URL path to documentation that explains how to perform the action.

Sample:
url_example
 
category_id
string
on success
The unique OCID associated with the category.

Sample:
ocid1.category.oc1..xxxxxxEXAMPLExxxxxx
 
compartment_id
string
on success
The OCID of the compartment.

Sample:
ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
 
compartment_name
string
on success
The name associated with the compartment.

Sample:
compartment_name_example
 
estimated_cost_saving
float
on success
The estimated cost savings, in dollars, for the resource action.

Sample:
1.2
 
extended_metadata
dictionary
on success
Additional metadata key/value pairs that you provide. They serve the same purpose and functionality as fields in the `metadata` object.
They are distinguished from `metadata` fields in that these can be nested JSON objects (whereas `metadata` fields are string/string maps only).
For example:
`{"CurrentShape": {"name":"VM.Standard2.16"}, "RecommendedShape": {"name":"VM.Standard2.8"}}`

 
id
string
on success
The unique OCID associated with the resource action.

Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
 
lifecycle_state
string
on success
The resource action's current state.

Sample:
ACTIVE
 
metadata
dictionary
on success
Custom metadata key/value pairs for the resource action.
**Metadata Example**
"metadata" : { "cpuRecommendedShape": "VM.Standard1.1", "computeMemoryUtilization": "26.05734124418388", "currentShape": "VM.Standard1.2", "instanceRecommendedShape": "VM.Standard1.1", "computeCpuUtilization": "7.930035319720132", "memoryRecommendedShape": "None" }

 
name
string
on success
The name assigned to the resource.

Sample:
name_example
 
recommendation_id
string
on success
The unique OCID associated with the recommendation.

Sample:
ocid1.recommendation.oc1..xxxxxxEXAMPLExxxxxx
 
resource_id
string
on success
The unique OCID associated with the resource.

Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
 
resource_type
string
on success
The kind of resource.

Sample:
resource_type_example
 
status
string
on success
The current status of the resource action.

Sample:
PENDING
 
time_created
string
on success
The date and time the resource action details were created, in the format defined by RFC3339.

Sample:
2013-10-20T19:20:30+01:00
 
time_status_begin
string
on success
The date and time that the resource action entered its current status. The format is defined by RFC3339.
For example, "The status of the resource action changed from `pending` to `current(ignored)` on this date and time."

Sample:
2013-10-20T19:20:30+01:00
 
time_status_end
string
on success
The date and time the current status will change. The format is defined by RFC3339.
For example, "The current `postponed` status of the resource action will end and change to `pending` on this date and time."

Sample:
2013-10-20T19:20:30+01:00
 
time_updated
string
on success
The date and time the resource action details were last updated, in the format defined by RFC3339.

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


Authors

  • Oracle (@oracle)