Skip to content

Triage provider-guide drift found by static checker #609

@caiopizzol

Description

@caiopizzol

The static drift checker in #608 found provider-guide drift across docs, sample links, and connector metadata.

This issue tracks the findings and follow-up work. Not every finding is a docs bug: some need connector/catalog changes, product decisions, or validated sample creation.

Current status

Latest sweep

Re-run on 2026-05-28 against current amp-labs/docs@main with the #608 checker overlaid.

Area Count Status
Doc/catalog action mismatches 3 Monday has amp-labs/connectors#3036; AWS and Greenhouse remain open
Broken sample links 5 Zendesk Support and Flatfile are fixed; 5 genuinely missing samples remain
Undocumented providers 29 Needs provider-by-provider triage
Total 37 Down from the first 40-finding sweep

Remaining high-signal items

Action mismatches

  • aws.mdx claims Write Actions, but live metadata reports support.write: false. Runtime not tested.
  • greenhouseJobBoard.mdx claims Proxy Actions, but metadata reports proxy: false; the guide is already excluded from nav, and connector source says it is not shipping yet.

Broken sample links still unresolved

These guides still point to missing samples. No typo or near-match sample paths were found.

  • drift
  • fourFour
  • outplay
  • paddle
  • seismic

Preferred fix: create validated samples in amp-labs/samples. If that is not practical yet, remove the dead links as a temporary docs cleanup.

Undocumented providers

29 catalog providers have no guide and no allowance. Highest priority (expose full read/write/proxy):

  • fastSpring
  • microsoftClientCredentials
  • zendeskChat

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions