Skip to content

Conversation

@lueschem
Copy link
Contributor

Description

This PR makes the usage of runner_org slightly more flexible:

runner_org: yes

as well as

runner_org: "yes"

is being accepted.

Reason: I have a slightly inflexible environment that just allows me to pass variables as key/value pairs where the value is always treated as string.

Remark: The change should do no harm as it is aligned with the when statements:

when: not runner_org

and

when: runner_org | bool

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Minor change (pipeline, tests, spelling ...)

How Has This Been Tested?

I have been running the playbook using different ways to specify runner_org.

MonolithProjects and others added 3 commits March 7, 2022 10:47
Be slightly more tolerant if the the input is
runner_org: "yes" # string
instead of
runner_org: yes # boolean
@MonolithProjects
Copy link
Owner

lgtm

@MonolithProjects MonolithProjects merged commit 2766fd7 into MonolithProjects:develop Mar 31, 2022
@MonolithProjects MonolithProjects mentioned this pull request Mar 31, 2022
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants