Skip to content

fix(flatfile): rename filatfile/amp.yml to flatfile/amp.yaml to match docs link#132

Merged
caiopizzol merged 1 commit into
amp-labs:mainfrom
caiopizzol:caiopizzol/fix-flatfile-sample-path
May 18, 2026
Merged

fix(flatfile): rename filatfile/amp.yml to flatfile/amp.yaml to match docs link#132
caiopizzol merged 1 commit into
amp-labs:mainfrom
caiopizzol:caiopizzol/fix-flatfile-sample-path

Conversation

@caiopizzol
Copy link
Copy Markdown
Contributor

Summary

Renames the Flatfile sample directory from the typo'd filatfile/ to flatfile/, and the file extension from .yml to .yaml, so the path matches what amp-labs/docs/src/provider-guides/flatfile.mdx already links to.

Today:

  • samples/filatfile/amp.yml exists (HTTP 200)
  • samples/flatfile/amp.yaml returns 404 — the path the docs guide references

After this PR, the docs link resolves. No content changes; pure path correction.

Verification

filatfile/amp.yml          HTTP 200   (current state — typo'd path)
flatfile/amp.yaml          HTTP 404   (current state — what docs link to)

Git records this as a rename of the existing file at 100% similarity.

During investigation I also exercised the Flatfile API-key connection end-to-end against the Ampersand production API: a proxy GET /v1/spaces through proxy.withampersand.com returned the same response as a direct call to api.x.flatfile.com/v1/spaces. That confirms the provider's connection + proxy flow works; it does not re-validate the specific read/write object claims in the manifest body. Those were not exercised here and are preserved as-is.

Related

The Flatfile sample was created under a typo'd directory name
('filatfile' instead of 'flatfile') with a .yml extension. The docs
guide at amp-labs/docs/src/provider-guides/flatfile.mdx links to
samples/blob/main/flatfile/amp.yaml, which currently returns 404
because the file is at /filatfile/amp.yml instead.

This rename moves the existing, well-formed Flatfile sample to the
path the docs already reference. No content changes.

Verified during investigation: the Flatfile connector connects with
an API-key auth scheme and proxies API calls end-to-end through
Ampersand. The existing manifest's specific read/write object claims
(events, jobs, environments, apps, spaces) were not exercised
end-to-end; this PR is a path correctness fix, not a re-validation
of the manifest's full contents.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant