oracle.oci.oci_file_storage_snapshot_facts – Fetches details about one or multiple Snapshot resources in Oracle Cloud Infrastructure¶
Note
This plugin is part of the oracle.oci collection (version 4.14.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_file_storage_snapshot_facts
.
New in version 2.9.0: of oracle.oci
Synopsis¶
Fetches details about one or multiple Snapshot resources in Oracle Cloud Infrastructure
Lists snapshots of the specified file system.
If snapshot_id is specified, the details of a single Snapshot will be returned.
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 |
---|---|---|
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.
|
|
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 . |
|
file_system_id
string
|
The OCID of the file system.
Required to list multiple snapshots.
|
|
lifecycle_state
string
|
|
Filter results by the specified lifecycle state. Must be a valid state for the resource type.
|
name
string
|
Use name along with the other options to return only resources that match the given name exactly.
|
|
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. |
|
snapshot_id
string
|
The OCID of the snapshot.
Required to get a specific snapshot.
aliases: id |
|
sort_order
string
|
|
The sort order to use, either 'asc' or 'desc', where 'asc' is ascending and 'desc' is descending. The default order is 'desc' except for numeric values.
|
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 |
Notes¶
Note
For OCI python sdk configuration, please refer to https://oracle-cloud-infrastructure-python-sdk.readthedocs.io/en/latest/configuration.html
Examples¶
- name: Get a specific snapshot
oci_file_storage_snapshot_facts:
# required
snapshot_id: "ocid1.snapshot.oc1..xxxxxxEXAMPLExxxxxx"
- name: List snapshots
oci_file_storage_snapshot_facts:
# required
file_system_id: "ocid1.filesystem.oc1..xxxxxxEXAMPLExxxxxx"
# optional
lifecycle_state: CREATING
sort_order: ASC
Return Values¶
Common return values are documented here, the following are the fields unique to this module:
Key | Returned | Description | |
---|---|---|---|
snapshots
complex
|
on success |
List of Snapshot resources
Sample:
[{'defined_tags': {'Operations': {'CostCenter': 'US'}}, 'file_system_id': 'ocid1.filesystem.oc1..xxxxxxEXAMPLExxxxxx', 'freeform_tags': {'Department': 'Finance'}, 'id': 'ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx', 'is_clone_source': True, 'lifecycle_details': 'lifecycle_details_example', 'lifecycle_state': 'CREATING', 'name': 'name_example', 'provenance_id': 'ocid1.provenance.oc1..xxxxxxEXAMPLExxxxxx', 'snapshot_time': '2013-10-20T19:20:30+01:00', 'snapshot_type': 'USER', 'time_created': '2013-10-20T19:20:30+01:00'}]
|
|
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'}}
|
|
file_system_id
string
|
on success |
The OCID of the file system from which the snapshot was created.
Sample:
ocid1.filesystem.oc1..xxxxxxEXAMPLExxxxxx
|
|
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 snapshot.
Sample:
ocid1.resource.oc1..xxxxxxEXAMPLExxxxxx
|
|
is_clone_source
boolean
|
on success |
Specifies whether the snapshot has been cloned. See Cloning a File System.
Sample:
True
|
|
lifecycle_details
string
|
on success |
Additional information about the current `lifecycleState`.
Sample:
lifecycle_details_example
|
|
lifecycle_state
string
|
on success |
The current state of the snapshot.
Sample:
CREATING
|
|
name
string
|
on success |
Name of the snapshot. This value is immutable.
Avoid entering confidential information.
Example: `Sunday`
Sample:
name_example
|
|
provenance_id
string
|
on success |
An OCID identifying the parent from which this snapshot was cloned. If this snapshot was not cloned, then the `provenanceId` is the same as the snapshot `id` value. If this snapshot was cloned, then the `provenanceId` value is the parent's `provenanceId`. See Cloning a File System.
Sample:
ocid1.provenance.oc1..xxxxxxEXAMPLExxxxxx
|
|
snapshot_time
string
|
on success |
The date and time the snapshot was taken, expressed in RFC 3339 timestamp format. This value might be the same or different from `timeCreated` depending on the following factors: - If the snapshot is created in the original file system directory. - If the snapshot is cloned from a file system. - If the snapshot is replicated from a file system.
Example: `2020-08-25T21:10:29.600Z`
Sample:
2013-10-20T19:20:30+01:00
|
|
snapshot_type
string
|
on success |
Specifies generation type of the snapshot.
Sample:
USER
|
|
time_created
string
|
on success |
The date and time the snapshot was created, expressed in RFC 3339 timestamp format.
Example: `2016-08-25T21:10:29.600Z`
Sample:
2013-10-20T19:20:30+01:00
|
Authors¶
Oracle (@oracle)