Open swoffish opened 1 year ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @Lunik @Shaps @lgatellier @marwatk @metanovii @nejch @scodeman @sh0shin @suukit @waheedi @zanssa click here for bot help
Hi @swoffish ,
Thanks for your feedback !
community.general's GitLab-related modules rely on python-gitlab, which doesn't support "expires_at" option yet for deploy keys API, as far as I know.
I suggest you to open an issue on python-gitlab GitHub project first.
Hi @swoffish ,
Thanks for your feedback !
community.general's GitLab-related modules rely on python-gitlab, which doesn't support "expires_at" option yet for deploy keys API, as far as I know.
I suggest you to open an issue on python-gitlab GitHub project first.
@lgatellier as mentioned in the other issue, python-gitlab can pass arbitrary API parameters to the server (for most endpoints). So it can be simply added here like the other arguments.
Hi @swoffish ,
Thanks for your feedback !
community.general's GitLab-related modules rely on python-gitlab, which doesn't support "expires_at" option yet for deploy keys API, as far as I know.
I suggest you to open an issue on python-gitlab GitHub project first.
@lgatellier as mentioned in the other issue, python-gitlab can pass arbitrary API parameters to the server (for most endpoints). So it can be simply added here like the other arguments.
Didn't know that, thanks!
Summary
Ability to set expires_at variable for deploy key.
With new configuration in gitlab the expiration key for deploy keys cannot be left blank or be invalid (past 6 months)
We can no longer utilize the module to create our deploy keys. Moved to using the uri module for an API call instead.
Issue Type
Feature Idea
Component Name
gitlab_deploy_key
Additional Information
Code of Conduct