oracle.oci.oci_golden_gate_deployment_actions – Perform actions on a Deployment 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_golden_gate_deployment_actions.

New in version 2.9.0: of oracle.oci

Synopsis

  • Perform actions on a Deployment resource in Oracle Cloud Infrastructure

  • For action=change_compartment, moves the Deployment into a different compartment within the same tenancy. When provided, If-Match is checked against ETag values of the resource. For information about moving resources between compartments, see Moving Resources Between Compartments.

  • For action=collect_deployment_diagnostic, collects the diagnostic of a Deployment. When provided, If-Match is checked against ETag values of the resource.

  • For action=start, starts a Deployment. When provided, If-Match is checked against ETag values of the resource.

  • For action=stop, stops a Deployment. When provided, If-Match is checked against ETag values of the resource.

  • For action=upgrade, upgrade a Deployment. 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.

Parameters

Parameter Choices/Defaults Comments
action
string / required
    Choices:
  • change_compartment
  • collect_deployment_diagnostic
  • start
  • stop
  • upgrade
The action to perform on the Deployment.
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.
bucket_name
string
Name of the bucket where the object is to be uploaded in the object storage
Required for action=collect_deployment_diagnostic.
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 being referenced.
Required for action=change_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.
deployment_id
string / required
A unique Deployment identifier.

aliases: id
diagnostic_name_prefix
string
Prefix of the diagnostic collected and uploaded to object storage
Required for action=collect_deployment_diagnostic.
namespace_name
string
Name of namespace that serves as a container for all of your buckets
Required for action=collect_deployment_diagnostic.
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
time_diagnostic_end
string
The time until which the diagnostic collection should collect the logs. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.
Applicable only for action=collect_deployment_diagnostic.
time_diagnostic_start
string
The time from which the diagnostic collection should collect the logs. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.
Applicable only for action=collect_deployment_diagnostic.
type
string
    Choices:
  • DEFAULT
  • CURRENT_RELEASE
The type of a deployment start
Required for action=start, action=stop, action=upgrade.
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: Perform action change_compartment on deployment
  oci_golden_gate_deployment_actions:
    # required
    compartment_id: "ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx"
    deployment_id: "ocid1.deployment.oc1..xxxxxxEXAMPLExxxxxx"
    action: change_compartment

- name: Perform action collect_deployment_diagnostic on deployment
  oci_golden_gate_deployment_actions:
    # required
    namespace_name: namespace_name_example
    bucket_name: bucket_name_example
    diagnostic_name_prefix: diagnostic_name_prefix_example
    deployment_id: "ocid1.deployment.oc1..xxxxxxEXAMPLExxxxxx"
    action: collect_deployment_diagnostic

    # optional
    time_diagnostic_start: time_diagnostic_start_example
    time_diagnostic_end: time_diagnostic_end_example

- name: Perform action start on deployment with type = DEFAULT
  oci_golden_gate_deployment_actions:
    # required
    type: DEFAULT

- name: Perform action start on deployment with type = CURRENT_RELEASE
  oci_golden_gate_deployment_actions:
    # required
    type: CURRENT_RELEASE

- name: Perform action stop on deployment with type = DEFAULT
  oci_golden_gate_deployment_actions:
    # required
    type: DEFAULT

- name: Perform action stop on deployment with type = CURRENT_RELEASE
  oci_golden_gate_deployment_actions:
    # required
    type: CURRENT_RELEASE

- name: Perform action upgrade on deployment with type = DEFAULT
  oci_golden_gate_deployment_actions:
    # required
    type: DEFAULT

- name: Perform action upgrade on deployment with type = CURRENT_RELEASE
  oci_golden_gate_deployment_actions:
    # required
    type: CURRENT_RELEASE

Return Values

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

Key Returned Description
deployment
complex
on success
Details of the Deployment resource acted upon by the current operation

Sample:
{'compartment_id': 'ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx', 'cpu_core_count': 56, 'defined_tags': {'Operations': {'CostCenter': 'US'}}, 'deployment_backup_id': 'ocid1.deploymentbackup.oc1..xxxxxxEXAMPLExxxxxx', 'deployment_diagnostic_data': {'bucket_name': 'bucket_name_example', 'diagnostic_state': 'IN_PROGRESS', 'namespace_name': 'namespace_name_example', 'object_name': 'object_name_example', 'time_diagnostic_end': '2013-10-20T19:20:30+01:00', 'time_diagnostic_start': '2013-10-20T19:20:30+01:00'}, 'deployment_type': 'OGG', 'deployment_url': 'deployment_url_example', 'description': 'description_example', 'display_name': 'display_name_example', 'fqdn': 'fqdn_example', 'freeform_tags': {'Department': 'Finance'}, 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'is_auto_scaling_enabled': True, 'is_healthy': True, 'is_latest_version': True, 'is_public': True, 'is_storage_utilization_limit_exceeded': True, 'license_model': 'LICENSE_INCLUDED', 'lifecycle_details': 'lifecycle_details_example', 'lifecycle_state': 'CREATING', 'lifecycle_sub_state': 'RECOVERING', 'nsg_ids': [], 'ogg_data': {'admin_username': 'admin_username_example', 'certificate': '-----BEGIN CERTIFICATE----MIIBIjANBgkqhkiG9w0BA..-----END PUBLIC KEY-----', 'deployment_name': 'deployment_name_example', 'ogg_version': 'ogg_version_example'}, 'private_ip_address': 'private_ip_address_example', 'public_ip_address': 'public_ip_address_example', 'storage_utilization_in_bytes': 56, 'subnet_id': 'ocid1.subnet.oc1..xxxxxxEXAMPLExxxxxx', 'system_tags': {}, 'time_created': '2013-10-20T19:20:30+01:00', 'time_updated': '2013-10-20T19:20:30+01:00', 'time_upgrade_required': '2013-10-20T19:20:30+01:00'}
 
compartment_id
string
on success
The OCID of the compartment being referenced.

Sample:
ocid1.compartment.oc1..xxxxxxEXAMPLExxxxxx
 
cpu_core_count
integer
on success
The Minimum number of OCPUs to be made available for this Deployment.

Sample:
56
 
defined_tags
dictionary
on success
Tags defined for this resource. Each key is predefined and scoped to a namespace.
Example: `{"foo-namespace": {"bar-key": "value"}}`

Sample:
{'Operations': {'CostCenter': 'US'}}
 
deployment_backup_id
string
on success
The OCID of the backup being referenced.

Sample:
ocid1.deploymentbackup.oc1..xxxxxxEXAMPLExxxxxx
 
deployment_diagnostic_data
complex
on success

   
bucket_name
string
on success
Name of the bucket where the object is to be uploaded in the object storage

Sample:
bucket_name_example
   
diagnostic_state
string
on success
The state of the deployment diagnostic collection.

Sample:
IN_PROGRESS
   
namespace_name
string
on success
Name of namespace that serves as a container for all of your buckets

Sample:
namespace_name_example
   
object_name
string
on success
Name of the diagnostic collected and uploaded to object storage

Sample:
object_name_example
   
time_diagnostic_end
string
on success
The time until which the diagnostic collection should collect the logs. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.

Sample:
2013-10-20T19:20:30+01:00
   
time_diagnostic_start
string
on success
The time from which the diagnostic collection should collect the logs. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.

Sample:
2013-10-20T19:20:30+01:00
 
deployment_type
string
on success
The type of deployment, the value determines the exact 'type' of service executed in the Deployment. NOTE: Use of the value 'OGG' is maintained for backward compatibility purposes. Its use is discouraged in favor of the equivalent 'DATABASE_ORACLE' value.

Sample:
OGG
 
deployment_url
string
on success
The URL of a resource.

Sample:
deployment_url_example
 
description
string
on success
Metadata about this specific object.

Sample:
description_example
 
display_name
string
on success
An object's Display Name.

Sample:
display_name_example
 
fqdn
string
on success
A three-label Fully Qualified Domain Name (FQDN) for a resource.

Sample:
fqdn_example
 
freeform_tags
dictionary
on success
A 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
The OCID of the deployment being referenced.

Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
 
is_auto_scaling_enabled
boolean
on success
Indicates if auto scaling is enabled for the Deployment's CPU core count.

Sample:
True
 
is_healthy
boolean
on success
True if all of the aggregate resources are working correctly.

Sample:
True
 
is_latest_version
boolean
on success
Indicates if the resource is the the latest available version.

Sample:
True
 
is_public
boolean
on success
True if this object is publicly available.

Sample:
True
 
is_storage_utilization_limit_exceeded
boolean
on success
Indicator will be true if the amount of storage being utilized exceeds the allowable storage utilization limit. Exceeding the limit may be an indication of a misconfiguration of the deployment's GoldenGate service.

Sample:
True
 
license_model
string
on success
The Oracle license model that applies to a Deployment.

Sample:
LICENSE_INCLUDED
 
lifecycle_details
string
on success
Describes the object's current state in detail. For example, it can be used to provide actionable information for a resource in a Failed state.

Sample:
lifecycle_details_example
 
lifecycle_state
string
on success
Possible lifecycle states.

Sample:
CREATING
 
lifecycle_sub_state
string
on success
Possible GGS lifecycle sub-states.

Sample:
RECOVERING
 
nsg_ids
list / elements=string
on success
An array of Network Security Group OCIDs used to define network access for either Deployments or Connections.

 
ogg_data
complex
on success

   
admin_username
string
on success
The GoldenGate deployment console username.

Sample:
admin_username_example
   
certificate
string
on success
A PEM-encoded SSL certificate.

Sample:
-----BEGIN CERTIFICATE----MIIBIjANBgkqhkiG9w0BA..-----END PUBLIC KEY-----
   
deployment_name
string
on success
The name given to the GoldenGate service deployment. The name must be 1 to 32 characters long, must contain only alphanumeric characters and must start with a letter.

Sample:
deployment_name_example
   
ogg_version
string
on success
Version of OGG

Sample:
ogg_version_example
 
private_ip_address
string
on success
The private IP address in the customer's VCN representing the access point for the associated endpoint service in the GoldenGate service VCN.

Sample:
private_ip_address_example
 
public_ip_address
string
on success
The public IP address representing the access point for the Deployment.

Sample:
public_ip_address_example
 
storage_utilization_in_bytes
integer
on success
The amount of storage being utilized (in bytes)

Sample:
56
 
subnet_id
string
on success
The OCID of the subnet being referenced.

Sample:
ocid1.subnet.oc1..xxxxxxEXAMPLExxxxxx
 
system_tags
dictionary
on success
The system tags associated with this resource, if any. The system tags are set by Oracle Cloud Infrastructure services. Each key is predefined and scoped to namespaces. For more information, see Resource Tags.
Example: `{orcl-cloud: {free-tier-retain: true}}`

 
time_created
string
on success
The time the resource was created. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.

Sample:
2013-10-20T19:20:30+01:00
 
time_updated
string
on success
The time the resource was last updated. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.

Sample:
2013-10-20T19:20:30+01:00
 
time_upgrade_required
string
on success
The date the existing version in use will no longer be considered as usable and an upgrade will be required. This date is typically 6 months after the version was released for use by GGS. The format is defined by RFC3339, such as `2016-08-25T21:10:29.600Z`.

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


Authors

  • Oracle (@oracle)