ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2026-05-11 04:04:13 +00:00
Code Activity

Shortened the notes about storing and accessing Jenkins token.

Browse source
This commit is contained in:
Sonal Karmakar 2026-04-28 17:01:21 +05:30 • committed by GitHub
parent 7697545efb
commit 5bc225bf5c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
plugins/modules/jenkins_credential.py
View file

@ -203,9 +203,9 @@ EXAMPLES = r"""
{{ token_result.id }},{{ token_result.name }},{{ token_result.token_uuid }},{{ token_result.token }} {{ token_result.id }},{{ token_result.name }},{{ token_result.token_uuid }},{{ token_result.token }}
# Note: # Note:
# The intended method is to store the Jenkins token in a secure place outside of the playbook, like an encrypted storage or a secrets vault, then retrieve it from there when needed. # Jenkins token is intended to be securely stored in encrypted storage or secrets vault outside the playbook, retrieved when needed.
# Examples below show how to access the token from the variable "token_result", and are NOT the intended approach for using the token to add credentials. # Examples below showcasing token retrieval from variable "token_result" are NOT how it should be used to add credentials.
# Data inside "token_result" will not be consistent or available across different playbooks and multiple executions. # Data in "token_result" is inconsistent and unavailable across different playbooks and multiple executions.
- name: Add CUSTOM scope credential - name: Add CUSTOM scope credential
community.general.jenkins_credential: community.general.jenkins_credential: