-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitlab_runner is not idempotent on first run after runner creation #5907
Labels
Comments
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 28, 2023
…rst run after runner creation This fix adds the missing parameter 'access_level' on runner creation. Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
Files identified in the description: If these files are incorrect, please update the |
ansibullbot
added
bug
This issue/PR relates to a bug
gitlab
module
module
plugins
plugin (any type)
source_control
labels
Jan 28, 2023
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 28, 2023
…rst run after runner creation This fix adds the missing parameter 'access_level' on runner creation. Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 28, 2023
…rst run after runner creation This fix adds the missing parameter 'access_level' on runner creation. Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 28, 2023
…rst run after runner creation With this fix the parameter 'access_level' of the module 'gitlab_runner' becomes optional. If unset, runner creation relies on GitLab's default value, if set, the runner gets created or updated with the specified access level. Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 28, 2023
…rst run after runner creation With this fix the parameter 'access_level' of the module 'gitlab_runner' becomes optional. If unset, runner creation relies on GitLab's default value, if set, the runner gets created or updated with the specified access level. Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 29, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 29, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 29, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 29, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 29, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 29, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
cfiehe
pushed a commit
to cfiehe/community.general
that referenced
this issue
Jan 30, 2023
…rst run after runner creation This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de>
patchback bot
pushed a commit
that referenced
this issue
Jan 30, 2023
…r creation (#5908) This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de> Co-authored-by: Christoph Fiehe <c.fiehe@eurodata.de> (cherry picked from commit 31ff3f6)
felixfontein
pushed a commit
that referenced
this issue
Jan 30, 2023
…not idempotent on first run after runner creation (#5922) Fixes #5907: gitlab_runner is not idempotent on first run after runner creation (#5908) This fix introduces the new boolean option 'access_level_on_creation'. It controls, whether the value of 'access_level' is used for runner registration or not. The option 'access_level' has been ignored on registration so far and was only used on updates. The user is informed by a deprecation warning, if the option is unspecified. For reasons of compatibility 'false' is assumed in that case. The option 'access_level_on_creation' will switch to 'true' for the next major release (community.general 7.0.0) Signed-off-by: Christoph Fiehe <c.fiehe@eurodata.de> Co-authored-by: Christoph Fiehe <c.fiehe@eurodata.de> (cherry picked from commit 31ff3f6) Co-authored-by: cfiehe <cfiehe@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Summary
On the first run after a GitLab runner creation, Ansible reports a change, although the configuration has not changed in the meanwhile. All subsequent runs on the other hand are idempotent.
Issue Type
Bug Report
Component Name
gitlab_runner
Ansible Version
Community.general Version
Configuration
CONFIG_FILE() = None
OS / Environment
Ubuntu 22.04
Steps to Reproduce
Just create a GitLab runner and re-execute the playbook.
Expected Results
Ansible should report no change on subsequent runs when the runner configuration has not changed.
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: