ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-04-18 16:31:26 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

[PR #9528/838cdaab backport][stable-10] lmn*: style adjustments (#9543)

Browse source 
lmn*: style adjustments (#9528)

* lmn*: style adjustments

* Apply suggestions from code review

* Apply suggestions from code review

Co-authored-by: Felix Fontein <felix@fontein.de>

---------

Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit 838cdaab42)

Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com>
This commit is contained in:
patchback[bot] 2025-01-07 18:45:30 +01:00 • committed by GitHub
parent 1f29fa2e39
commit 75f649648e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
43 changed files with 440 additions and 378 deletions
Download patch file Download diff file Expand all files Collapse all files

25
plugins/modules/mqtt.py
View file

@ -53,8 +53,8 @@ options:
payload:
type: str
description:
- Payload. The special string V("None") may be used to send a NULL (that is, empty) payload which is useful to simply notify with the O(topic)
or to clear previously retained messages.
- Payload. The special string V("None") may be used to send a NULL (that is, empty) payload which is useful to simply
notify with the O(topic) or to clear previously retained messages.
required: true
qos:
type: str
@ -64,29 +64,30 @@ options:
choices: ["0", "1", "2"]
retain:
description:
- Setting this flag causes the broker to retain (in other words keep) the message so that applications that subsequently subscribe to the topic can
received the last retained message immediately.
- Setting this flag causes the broker to retain (in other words keep) the message so that applications that subsequently
subscribe to the topic can received the last retained message immediately.
type: bool
default: false
ca_cert:
type: path
description:
- The path to the Certificate Authority certificate files that are to be treated as trusted by this client. If this is the only option given
then the client will operate in a similar manner to a web browser. That is to say it will require the broker to have a certificate signed
by the Certificate Authorities in ca_certs and will communicate using TLS v1, but will not attempt any form of authentication. This provides
basic network encryption but may not be sufficient depending on how the broker is configured.
- The path to the Certificate Authority certificate files that are to be treated as trusted by this client. If this
is the only option given then the client will operate in a similar manner to a web browser. That is to say it will
require the broker to have a certificate signed by the Certificate Authorities in ca_certs and will communicate using
TLS v1, but will not attempt any form of authentication. This provides basic network encryption but may not be sufficient
depending on how the broker is configured.
aliases: [ca_certs]
client_cert:
type: path
description:
- The path pointing to the PEM encoded client certificate. If this is not None it will be used as client information for TLS based authentication.
Support for this feature is broker dependent.
- The path pointing to the PEM encoded client certificate. If this is not None it will be used as client information
for TLS based authentication. Support for this feature is broker dependent.
aliases: [certfile]
client_key:
type: path
description:
- The path pointing to the PEM encoded client private key. If this is not None it will be used as client information for TLS based authentication.
Support for this feature is broker dependent.
- The path pointing to the PEM encoded client private key. If this is not None it will be used as client information
for TLS based authentication. Support for this feature is broker dependent.
aliases: [keyfile]
tls_version:
description: