Open sjaakvandenberg 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 @LennertMertens @Lunik @Shaps @dj-wasabi @lgatellier @marwatk @metanovii @nejch @scodeman @sh0shin @stgrace @suukit @waheedi @zanssa click here for bot help
hi @sjaakvandenberg Thanks for reporting this issue.
That version of community.general is way too old. Could you please try and replicate the problem using the most recent version (7.1.0)? Thanks in advance.
As described in #7220 i got the same issue, the ssh key is not updated if it uses the same name.
As a workaround:
In your playbook you use sshkey_name: pubkey
for all keys (20230510c, 20230510b and "Admin Two (project.url)").
If you give them different names this should still work with the current implementation.
Summary
When I try to update the SSH key for an existing Gitlab CE user using the
gitlab_user
module from the general collection (4.8.0), the change is not detected and the SSH keys aren't updated.Issue Type
Bug Report
Component Name
gitlab_user
Ansible Version
Community.general Version
Configuration
OS / Environment
Rocky 8
Steps to Reproduce
Example playbook:
Existing user in Gitlab CE project with username
admin2
and no SSH keys.Run 1 (SSH key is set for the first time):
RUN 2 (after updating SSH pubkey in play.yml)
Expected Results
I expected the SSH pubkey of the
admin2
user would update the existing key (with comment 20230510b) to the new key (with comment 20230510c).Actual Results
Code of Conduct