Follow-up from "Improve Azure Key Vault docs"
The following discussion from !134578 (merged) should be addressed:
-
@anton started a discussion: (+4 comments) Thought (non-blocking): As per my testing in #424746 (comment 1632270420), it seems that this feature has been broken since it was introduced?
Some users might see this introduced line and try using this feature on GitLab/GitLab Runner 16.3 - and its highly likely they will run into the
JWT token is invalid or malformed
error.I've attempted to address this in the newly created troubleshooting section of this MR, but its a reactive approach.
Should we be more proactive here, and ensure users start with a GitLab/GitLab Runner version combination (16.6+) that works from the get go so they don't see the
JWT token is invalid or malformed
error at all? I'm not sure how we can do that in the docs, or even how to word it. Hence, sharing my thoughts in case we want to address that.
The key comment:
Let's get these docs in for now, and I'll throw in a quick note at the top of the page warning that the feature probably doesn't work, but that a fix is scheduled for a future release. I'll create a followup from this thread to make sure we don't forget to update this page when the fix IS released and in production.