Discuss: Global prefixes for all metadata?

[leggetter]

For webhooks, Outpost supports a custom prefix (e.g. my-custom-prefix-topic) for Outpost headers. However, we do not have a custom prefix for other event destination types. Should the custom prefix be a global setting and be applied to HTTP headers, and all Outpost-specific metadata? (e.g. topic fields)

[alexbouchardd]

The only purpose of prefix is to avoid conflict, if the destination doesn't have "default" values as metadata like HTTP then no, I don't think there should be a prefix

[leggetter]

Avoid conflict and clear identity - sometimes branding.

Where this came from: from a conflict perspective, we need more clarity about how topics are identified on different on publish queues and destination types.

[alexbouchardd]

We should have default metadata, just not prefixed. One of those could be publisher: $ORGANIZATION_NAME if you need to identify. Also the assumption is that the destination implies it's use for instance your SQS queue would be called "acme_events" or something like that