Improve clarity on gitlab ee / ce webhook configurations #504
Conversation
Vercel Previews Deployed
|
|
I would also imagine that this should be back-ported into previous versions, but I wanted to ensure the wording was acceptable before doing a mass edit back in time! |
Broken Link CheckerNo broken links found! 🎉 |
There was a problem hiding this comment.
The wording is identical, what is added is a header in the troubleshooting section that provides details on the error message. This is great because it could help customers search for the issue more easily.
Thank you!
Please evaluate the targets for backporting.
EDIT: Upon reflection, I believe we do not need to backport this change. The change is merely stylistic / adding further context - which is great. But the information is already available in previous releases.
So I suggest: Lets pragmatically not backport :)
|
When previewing these changes in Vercel, I see this on the troubleshooting page: 
I can't see any obvious formatting issues in the markdown, and don't have visibility on any logs to see why this might be the case. Is anyone able to cast any light on this? Happy to work on it if it's a 'me' problem. 😄 |
| @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA | |||
|
|
|||
| Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. | |||
|
|
|||
| ## GitLab CE / GitLab EE | |||
|
|
|||
| ### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: <GITLAB INSTANCE HOSTNAME> | |||
There was a problem hiding this comment.
🚧 This header starts with an opening " but never closes it.
As per discussion on Slack, moving the information about "Allow requests to the local network from hooks and service" in Gitlab self hosted options into troubleshooting to better alert the user as to why they would need to do this.
In discussions, it appears that a couple of folks have missed the significance of that section of the docs due to it not being explicitly related to the 422 error seen in the TFE UI.
This PR will remove that ambiguity by specifically calling out the error message and the resolution.