Skip to content

feat(config): add mapToName to BaseReadConfigObject#358

Open
RajatPawar wants to merge 1 commit into
mainfrom
feat/install-config-mapToName
Open

feat(config): add mapToName to BaseReadConfigObject#358
RajatPawar wants to merge 1 commit into
mainfrom
feat/install-config-mapToName

Conversation

@RajatPawar

Copy link
Copy Markdown
Contributor

Summary

Adds optional mapToName to BaseReadConfigObject so an installation can rename a read object's delivered name per-customer (mirrors the existing manifest-level field on IntegrationObject).

Motivation

Today object-level mapToName only exists on the manifest. Builders who want per-customer object aliases — e.g. Aurasell delivering custom event types under their internal naming scheme — have to either declare every variant in the manifest or accept the provider object name on the wire.

This is the first half of the install-level mapToName work. The server PR ([amp-labs/server#TBD]) consumes the new field by updating getMappedObjectName to consult the installation's ReadConfigObject.MapToName first, falling back to the revision's mapping.

Changes

  • config/config.yaml — add mapToName to BaseReadConfigObject.
  • config/generated/config.json — regen.
  • api/generated/api.json — regen (inlined references).

Test plan

  • Schema validation (make lint)
  • Consumed by amp-labs/server PR before merge

Mirrors the manifest's IntegrationObject.mapToName so installations can
rename a read object's delivered name per-customer. Optional; the server
will fall through to the manifest's mapToName if the install doesn't
set one.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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