cloudera.cloud.de_info module – Gather information about CDP Data Engineering Services
Note
This module is part of the cloudera.cloud collection (version 3.3.0).
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 cloudera.cloud.
To use it in a playbook, specify: cloudera.cloud.de_info.
New in cloudera.cloud 1.5.0
Synopsis
Gather information about CDP Data Engineering Services
Parameters
Parameter |
Comments |
|---|---|
If provided, the Cloudera on cloud API will use this value as its access key. If not provided, the API will attempt to use the value from the environment variable Required if Mutually exclusive with |
|
If a cluster_id is provided, that Data Engineering Service will be described Mutually exclusive with name and env_name |
|
If provided, the Cloudera on cloud API will use this value as its credentials path. If not provided, the API will attempt to use the value from the environment variable Default: |
|
If Choices:
|
|
The Cloudera on cloud API endpoint to use. If not provided, the API will attempt to use the value from the environment variable Mutually exclusive with |
|
Specify the Cloudera on cloud API endpoint region. See Cloudera Control Plane regions for more information. If not provided, the API will attempt to use the value from the environment variable
Mutually exclusive with Choices:
|
|
Verify the TLS certificates for the Cloudera on cloud API endpoint. Choices:
|
|
If an env_name is provided, the Data Engineering Service for that Environment will be described Mutually exclusive with name and cluster_id |
|
The HTTP user agent to use for Cloudera on cloud API requests. Default: |
|
If a name is provided, that Data Engineering Service will be described Must be the string name of the CDE service Mutually exclusive with cluster_id and env_name |
|
If provided, the Cloudera on cloud API will use this value as its private key. If not provided, the API will attempt to use the value from the environment variable Required if |
|
If provided, the Cloudera on cloud API will use this value as its profile. If not provided, the API will attempt to use the value from the environment variable Default: |
|
Legacy CDPy SDK error handling. Choices:
|
Examples
# Note: These examples do not set authentication details.
# List basic information about all Data Engineering Services
- cloudera.cloud.de_info:
# Gather detailed information about a named Data Engineering Service
- cloudera.cloud.de_info:
name: example-de-service
# Gather detailed information about a Data Engineering Service using a cluster ID
- cloudera.cloud.de_info:
cluster_id: cluster-12345
# Gather detailed information about a Data Engineering Service using an Environment name
- cloudera.cloud.de_info:
env_name: my-environment
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
Returns the captured CDP SDK log. Returned: when supported |
|
Returns a list of each line of the captured CDP SDK log. Returned: when supported |
|
The information about the named Data Engineering Service or Data Engineering Services Returned: always |
|
Base location for the service backup archives Returned: when available |
|
The cloud platform where the CDE service is enabled Returned: when available |
|
FQDN of the CDE service Returned: when available |
|
Cluster Id of the CDE Service Returned: always |
|
CRN of the creator Returned: when available |
|
Email address of the creator of the CDE service Returned: when available |
|
Endpoint of Data Lake Atlas Returned: when available |
|
The Data lake file system Returned: when available |
|
Timestamp of service enabling Returned: when available |
|
CRN of the environment Returned: when available |
|
CDP Environment Name Returned: always |
|
Comma-separated CIDRs that would be allowed to access the load balancer Returned: when available |
|
Location for the log files of jobs Returned: when available |
|
Name of the CDE Service Returned: always |
|
Network outbound type Returned: when available |
|
The “true” value indicates that the previous version of the CDE service was requested to be deployed Returned: when available |
|
If true, the CDE service was created with fully private Azure services Returned: when available |
|
If true, the CDE endpoint was created in a publicly accessible subnet Returned: when available |
|
Resources details of CDE Service Returned: when available |
|
Resource details for the nodes used in All Purpose Virtual Clusters Returned: when available |
|
CPU Requests for the entire CDE service quota Returned: when available |
|
Initial instances for the CDE service Returned: when available |
|
Initial Spot Instances for the CDE Service Returned: when available |
|
Instance type of the CDE service Returned: when available |
|
Maximum instances for the CDE service Returned: when available |
|
Maximum Number of Spot instances Returned: when available |
|
Memory requests for the entire CDE service quota Returned: when available |
|
Minimum Instances for the CDE service Returned: when available |
|
Minimum number of spot instances for the CDE service Returned: when available |
|
Resource Pool for the CDE service Returned: when available |
|
Root Volume Size Returned: when available |
|
If true, SSD would have been be used for workload filesystem Returned: when available |
|
Status of the CDE service Returned: always |
|
List of Subnet IDs of the CDP subnets used by the kubernetes worker node Returned: when available |
|
CDP tenant ID Returned: when available |
|
List of CIDRs that would be allowed to access kubernetes master API server Returned: when available |
|
If true, diagnostic information about job and query execution is sent to Cloudera Workload Manager Returned: when available |