Link the Dotfile and Segment connector docs
Both now have a page on probo.com, so their provider cards in the Add Source dialog carry a Documentation link. The slugs match the page filenames, which is what keeps the link off a 404. Google Analytics and Square stay unlinked: they are OAuth connectors and no OAuth connector has a docs page yet, so there is nothing to point at. Signed-off-by: Aurélien Sibiril <81782+aureliensibiril@users.noreply.github.com>
This commit is contained in:
@@ -32,9 +32,10 @@ import (
|
|||||||
|
|
||||||
func dotfileRegistration() *Registration {
|
func dotfileRegistration() *Registration {
|
||||||
return &Registration{
|
return &Registration{
|
||||||
Provider: coredata.ConnectorProviderDotfile,
|
Provider: coredata.ConnectorProviderDotfile,
|
||||||
DisplayName: "Dotfile",
|
DisplayName: "Dotfile",
|
||||||
SupportsAPIKey: true,
|
DocumentationURL: accessReviewDocsURL("dotfile"),
|
||||||
|
SupportsAPIKey: true,
|
||||||
// Dotfile authenticates with the API key in the X-DOTFILE-API-KEY
|
// Dotfile authenticates with the API key in the X-DOTFILE-API-KEY
|
||||||
// header rather than Authorization: Bearer. APIKeyHeader makes the
|
// header rather than Authorization: Bearer. APIKeyHeader makes the
|
||||||
// APIKeyConnection send that header and omit Authorization. The key is
|
// APIKeyConnection send that header and omit Authorization. The key is
|
||||||
|
|||||||
@@ -33,9 +33,10 @@ import (
|
|||||||
|
|
||||||
func segmentRegistration() *Registration {
|
func segmentRegistration() *Registration {
|
||||||
return &Registration{
|
return &Registration{
|
||||||
Provider: coredata.ConnectorProviderSegment,
|
Provider: coredata.ConnectorProviderSegment,
|
||||||
DisplayName: "Segment",
|
DisplayName: "Segment",
|
||||||
SupportsAPIKey: true,
|
DocumentationURL: accessReviewDocsURL("segment"),
|
||||||
|
SupportsAPIKey: true,
|
||||||
// Segment authenticates with a Public API token as the default
|
// Segment authenticates with a Public API token as the default
|
||||||
// Authorization: Bearer scheme, so no APIKeyHeader. The token is bound
|
// Authorization: Bearer scheme, so no APIKeyHeader. The token is bound
|
||||||
// to one workspace, but the workspace's region selects the API host
|
// to one workspace, but the workspace's region selects the API host
|
||||||
|
|||||||
Reference in New Issue
Block a user