feat: add PlatformEventMigration to registry#1807
Open
aalhadxx wants to merge 1 commit into
Open
Conversation
Adds PlatformEventMigration metadata type to the registry with values verified from a live Salesforce org describe. Verified via `sf org list metadata-types` from a connected org: - directoryName: platformEventMigrations - suffix: platformEventMigration - xmlName: PlatformEventMigration - inFolder: false Registry validation: 29,124 passing Manual testing: CLI successfully resolves the type (previously threw RegistryError)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds PlatformEventMigration to the metadata registry.
What issues does this PR fix or reference?
Closes a gap in METADATA_SUPPORT.md.
Registry values
Values were verified from a live org describe (sf org list metadata-types):
Validation
Is there anything else we should know?
Live org testing showed the type is recognized by the CLI after registry addition. The org returned "Entity type not available in this API version" — confirming the registry entry is structurally correct and the limitation is at the org/API level, not the registry.