Support Kafka topic configuration migration/synchronization.

[BYK]

There are several topic configurations that are required for efficient or correct message processing in certain circumstances:

• log compaction settings for the commit log topic
• timestamp type for topics that are consumed as ticks subscription data

Use https://segment.com/blog/easier-management-of-Kafka-topics-with-topicctl/

/cc @chadwhitacre @mattrobenolt @getsentry/sns

[mattrobenolt]

We have plans to execute on work for this, we just haven't done it yet.

[BYK]

Hence the "Status: Accepted" label :) Is this on @getsentry/single-tenant's roadmap or should I keep it on myself?

[mattrobenolt]

I guess we don't have this in Asana, I'll figure out how to add this. We've talked about it very recently, I guess didn't track it anywhere, but I'd say yeah, this is our responsibility.

[BYK]

I guess we don't have this in Asana, I'll figure out how to add this.

I just moved this from Asana (was tracked on an OSS Team board) for the sake of external visibility and our effort to use GitHub more. Up to you if you still want a copy there but they should be linked.

/cc @chadwhitacre

[mattrobenolt]

That's fine, I dunno where we stand on the tools we use, but I know all of our stuff is in Asana these days. I don't make these decisions. I don't even know how to use the tools.

[chadwhitacre]

Does this belong in onpremise or should we move to sentry? Where will the code live?

[BYK]

I would assume the code to live here at the beginning until it is more broadly adopted (may move into its own repo or under getsentry/sentry).