Skip to content
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

registration-token deprecation #1796

Closed
pgraemer opened this issue Nov 17, 2023 · 4 comments · Fixed by #1799
Closed

registration-token deprecation #1796

pgraemer opened this issue Nov 17, 2023 · 4 comments · Fixed by #1799

Comments

@pgraemer
Copy link

gitlab deprecated the registration-token.
for further reading check this:

https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html

@neilkuan
Copy link
Owner

Hi @pgraemer , Thanks for report this issue.
I already add new gitlabRunnerVersion props and helper function to resolve this issue at [email protected].
Cloud you try and give me a review ?! let me know what did you think. thank you.

@pgraemer
Copy link
Author

hey @neilkuan, just reviewed your changes and tested the latest version.

maybe one suggested change:
considering the default gitlabRunnerImage is latest - why not set the gitlabRunnerVersion also to latest as a default?

@neilkuan
Copy link
Owner

hey @neilkuan, just reviewed your changes and tested the latest version.

maybe one suggested change: considering the default gitlabRunnerImage is latest - why not set the gitlabRunnerVersion also to latest as a default?

because I didn't know what is latest( 16.1.0, 16.1.1 etc... ) version for gitlabRunnerVersion. lol

@pgraemer
Copy link
Author

well i know that u cannot estimate the version of latest :D

but the version check is now also somewhat ambiguous as you could also even set a specific flag like useOldRegistrationFlow to solve it.

if i have time i try to propose a PR to showcase what i've meant :)

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 a pull request may close this issue.

2 participants