community.general.bitbucket_pipeline_variable module – Manages Bitbucket pipeline variables

Note

This module is part of the community.general collection (version 4.8.3).

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 community.general.

To use it in a playbook, specify: community.general.bitbucket_pipeline_variable.

Synopsis

  • Manages Bitbucket pipeline variables.

Parameters

Parameter

Comments

client_id

string

The OAuth consumer key.

If not set the environment variable BITBUCKET_CLIENT_ID will be used.

client_secret

string

The OAuth consumer secret.

If not set the environment variable BITBUCKET_CLIENT_SECRET will be used.

name

string / required

The pipeline variable name.

password

string

added in 4.0.0 of community.general

The App password.

If not set the environment variable BITBUCKET_PASSWORD will be used.

repository

string / required

The repository name.

secured

boolean

Whether to encrypt the variable value.

Choices:

  • no ← (default)

  • yes

state

string / required

Indicates desired state of the variable.

Choices:

  • absent

  • present

user

string

added in 4.0.0 of community.general

The username.

If not set the environment variable BITBUCKET_USERNAME will be used.

value

string

The pipeline variable value.

workspace

aliases: username

string / required

The repository owner.

Alias username has been deprecated and will become an alias of user in community.general 6.0.0.

Notes

Note

  • Check mode is supported.

  • For secured values return parameter changed is always True.

  • Bitbucket OAuth consumer key and secret can be obtained from Bitbucket profile -> Settings -> Access Management -> OAuth.

  • Bitbucket App password can be created from Bitbucket profile -> Personal Settings -> App passwords.

  • If both OAuth and Basic Auth credentials are passed, OAuth credentials take precedence.

Examples

- name: Create or update pipeline variables from the list
  community.general.bitbucket_pipeline_variable:
    repository: 'bitbucket-repo'
    workspace: bitbucket_workspace
    name: '{{ item.name }}'
    value: '{{ item.value }}'
    secured: '{{ item.secured }}'
    state: present
  with_items:
    - { name: AWS_ACCESS_KEY, value: ABCD1234, secured: False }
    - { name: AWS_SECRET, value: qwe789poi123vbn0, secured: True }

- name: Remove pipeline variable
  community.general.bitbucket_pipeline_variable:
    repository: bitbucket-repo
    workspace: bitbucket_workspace
    name: AWS_ACCESS_KEY
    state: absent

Authors

  • Evgeniy Krysanov (@catcombo)