oracle.oci.oci_opsi_exadata_insights_actions – Perform actions on an ExadataInsights resource in Oracle Cloud Infrastructure¶
Note
This plugin is part of the oracle.oci collection (version 5.0.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_opsi_exadata_insights_actions
.
New in version 2.9.0: of oracle.oci
Synopsis¶
Perform actions on an ExadataInsights resource in Oracle Cloud Infrastructure
For action=change, moves an Exadata insight resource from one compartment identifier to another. When provided, If-Match is checked against ETag values of the resource.
Requirements¶
The below requirements are needed on the host that executes this module.
python >= 3.6
Python SDK for Oracle Cloud Infrastructure https://oracle-cloud-infrastructure-python-sdk.readthedocs.io
Parameters¶
Parameter | Choices/Defaults | Comments |
---|---|---|
action
string
/ required
|
|
The action to perform on the ExadataInsights.
|
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
|
|
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
|
|
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
/ required
|
The OCID of the compartment into which the resource should be moved.
|
|
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 . |
|
exadata_insight_id
string
/ required
|
Unique Exadata insight identifier
aliases: id |
|
realm_specific_endpoint_template_enabled
boolean
|
|
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. |
|
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
|
|
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.
|
Notes¶
Note
For OCI python sdk configuration, please refer to https://oracle-cloud-infrastructure-python-sdk.readthedocs.io/en/latest/configuration.html
Examples¶
- name: Perform action change on exadata_insights
oci_opsi_exadata_insights_actions:
# required
exadata_insight_id: "ocid1.exadatainsight.oc1..xxxxxxEXAMPLExxxxxx"
compartment_id: "ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx"
action: change
Return Values¶
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description | |
---|---|---|---|
exadata_insights
complex
|
on success |
Details of the ExadataInsights resource acted upon by the current operation
Sample:
{'compartment_id': 'ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx', 'defined_tags': {'Operations': {'CostCenter': 'US'}}, 'enterprise_manager_bridge_id': 'ocid1.enterprisemanagerbridge.oc1..xxxxxxEXAMPLExxxxxx', 'enterprise_manager_entity_display_name': 'enterprise_manager_entity_display_name_example', 'enterprise_manager_entity_identifier': 'enterprise_manager_entity_identifier_example', 'enterprise_manager_entity_name': 'enterprise_manager_entity_name_example', 'enterprise_manager_entity_type': 'enterprise_manager_entity_type_example', 'enterprise_manager_identifier': 'enterprise_manager_identifier_example', 'entity_source': 'EM_MANAGED_EXTERNAL_EXADATA', 'exadata_display_name': 'exadata_display_name_example', 'exadata_infra_id': 'ocid1.exadatainfra.oc1..xxxxxxEXAMPLExxxxxx', 'exadata_infra_resource_type': 'cloudExadataInfrastructure', 'exadata_name': 'exadata_name_example', 'exadata_rack_type': 'FULL', 'exadata_shape': 'exadata_shape_example', 'exadata_type': 'DBMACHINE', 'freeform_tags': {'Department': 'Finance'}, 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'is_auto_sync_enabled': True, 'is_virtualized_exadata': True, 'lifecycle_details': 'lifecycle_details_example', 'lifecycle_state': 'CREATING', 'status': 'DISABLED', 'system_tags': {}, 'time_created': '2013-10-20T19:20:30+01:00', 'time_updated': '2013-10-20T19:20:30+01:00'}
|
|
compartment_id
string
|
on success |
Compartment identifier of the Exadata insight resource
Sample:
ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
|
|
defined_tags
dictionary
|
on success |
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: `{"foo-namespace": {"bar-key": "value"}}`
Sample:
{'Operations': {'CostCenter': 'US'}}
|
|
enterprise_manager_bridge_id
string
|
on success |
OPSI Enterprise Manager Bridge OCID
Sample:
ocid1.enterprisemanagerbridge.oc1..xxxxxxEXAMPLExxxxxx
|
|
enterprise_manager_entity_display_name
string
|
on success |
Enterprise Manager Entity Display Name
Sample:
enterprise_manager_entity_display_name_example
|
|
enterprise_manager_entity_identifier
string
|
on success |
Enterprise Manager Entity Unique Identifier
Sample:
enterprise_manager_entity_identifier_example
|
|
enterprise_manager_entity_name
string
|
on success |
Enterprise Manager Entity Name
Sample:
enterprise_manager_entity_name_example
|
|
enterprise_manager_entity_type
string
|
on success |
Enterprise Manager Entity Type
Sample:
enterprise_manager_entity_type_example
|
|
enterprise_manager_identifier
string
|
on success |
Enterprise Manager Unique Identifier
Sample:
enterprise_manager_identifier_example
|
|
entity_source
string
|
on success |
Source of the Exadata system.
Sample:
EM_MANAGED_EXTERNAL_EXADATA
|
|
exadata_display_name
string
|
on success |
The user-friendly name for the Exadata system. The name does not have to be unique.
Sample:
exadata_display_name_example
|
|
exadata_infra_id
string
|
on success |
The OCID of the Exadata Infrastructure.
Sample:
ocid1.exadatainfra.oc1..xxxxxxEXAMPLExxxxxx
|
|
exadata_infra_resource_type
string
|
on success |
OCI exadata infrastructure resource type
Sample:
cloudExadataInfrastructure
|
|
exadata_name
string
|
on success |
The Exadata system name. If the Exadata systems managed by Enterprise Manager, the name is unique amongst the Exadata systems managed by the same Enterprise Manager.
Sample:
exadata_name_example
|
|
exadata_rack_type
string
|
on success |
Exadata rack type.
Sample:
FULL
|
|
exadata_shape
string
|
on success |
The shape of the Exadata Infrastructure.
Sample:
exadata_shape_example
|
|
exadata_type
string
|
on success |
Operations Insights internal representation of the the Exadata system type.
Sample:
DBMACHINE
|
|
freeform_tags
dictionary
|
on success |
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: `{"bar-key": "value"}`
Sample:
{'Department': 'Finance'}
|
|
id
string
|
on success |
Exadata insight identifier
Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
|
|
is_auto_sync_enabled
boolean
|
on success |
Set to true to enable automatic enablement and disablement of related targets from Enterprise Manager. New resources (e.g. Database Insights) will be placed in the same compartment as the related Exadata Insight.
Sample:
True
|
|
is_virtualized_exadata
boolean
|
on success |
true if virtualization is used in the Exadata system
Sample:
True
|
|
lifecycle_details
string
|
on success |
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
Sample:
lifecycle_details_example
|
|
lifecycle_state
string
|
on success |
The current state of the Exadata insight.
Sample:
CREATING
|
|
status
string
|
on success |
Indicates the status of an Exadata insight in Operations Insights
Sample:
DISABLED
|
|
system_tags
dictionary
|
on success |
System tags for this resource. Each key is predefined and scoped to a namespace. Example: `{"orcl-cloud": {"free-tier-retained": "true"}}`
|
|
time_created
string
|
on success |
The time the the Exadata insight was first enabled. An RFC3339 formatted datetime string
Sample:
2013-10-20T19:20:30+01:00
|
|
time_updated
string
|
on success |
The time the Exadata insight was updated. An RFC3339 formatted datetime string
Sample:
2013-10-20T19:20:30+01:00
|
Authors¶
Oracle (@oracle)