cloudera.exe.supported lookup – Get support matrix details

Note

This lookup plugin is part of the cloudera.exe collection (version 3.0.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.exe..

To use it in a playbook, specify: cloudera.exe.supported.

New in cloudera.exe 3.0.0

Synopsis

  • Retrieve support matrix details for Cloudera Manager, Runtime, or Data Services versions.

Terms

Parameter

Comments

Terms

string

The categories to return from the support matrix.

All category entries will be flattened into a single list.

If undefined, all categories will be returned.

Choices:

  • "browsers"

  • "databases"

  • "jdks"

  • "kubernetes"

  • "operating_systems"

  • "processor"

  • "products"

Keyword parameters

This describes keyword parameters of the lookup. These are the values key1=value1, key2=value2 and so on in the following examples: lookup('cloudera.exe.supported', key1=value1, key2=value2, ...) and query('cloudera.exe.supported', key1=value1, key2=value2, ...)

Parameter

Comments

product

string / required

The anchor product for the support matrix.

Choices:

  • "cloudera_manager"

  • "cloudera_runtime"

  • "cloudera_data_services"

raw_filters

list / elements=string

Additional raw filters to add to the support matrix URL.

Each filter will be appended to the URL, delimited by colons (;).

timeout

integer

Query timeout (seconds)

Default: 30

version

string / required

The version of the product

Notes

Note

  • When keyword and positional parameters are used together, positional parameters must be listed before keyword parameters: lookup('cloudera.exe.supported', term1, term2, key1=value1, key2=value2) and query('cloudera.exe.supported', term1, term2, key1=value1, key2=value2)

Examples

Return Value

Key

Description

Return value

list / elements=list

The contents of the license.

Returned: success

Authors

  • Cloudera Labs

Hint

Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.