-
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
fix(modules/gitlab_runners): pass paused to gitlab #8648
fix(modules/gitlab_runners): pass paused to gitlab #8648
Conversation
02aa8ee
to
8f20094
Compare
TODOs (for me):
|
8f20094
to
7022cdc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution!
7022cdc
to
d4df47e
Compare
If nobody objects, I'll merge this in 1-2 weeks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Backport to stable-8: 💚 backport PR created✅ Backport PR branch: Backported as #8700 🤖 @patchback |
(cherry picked from commit b6c6253)
Backport to stable-9: 💚 backport PR created✅ Backport PR branch: Backported as #8701 🤖 @patchback |
@ap-wtioit thanks for your contribution! |
(cherry picked from commit b6c6253)
SUMMARY
The paused module parameter needs to passed to the create_or_update method to work.
As of now (gitlab 17.1.0)
active: False
is still working. But the gitlab_runner module silently ignoredpaused: True
and always responded withNo need to update the runner ...
if a runner was updated with a changed paused attribute. Creating a runner withpaused: True
also did not create a runner in paused state.ISSUE TYPE
COMPONENT NAME
gitlab_runner
ADDITIONAL INFORMATION
paused: True
has the runner not paused in gitlab after creationOr
paused: True
states:No need to update the runner ...
Info @wt-io-it