Topic config `redpanda.remote.readreplica` is never included in metadata

[patrickangeles]

Version & Environment

22.3

What went wrong?

When creating a read replica topic, we set a parameter redpanda.remote.readreplica=bucketname. This parameter is never returned in topic metadata queries, which plays badly with tools like Terraform which does a diff between current and desired state.

JIRA Link: CORE-1131

[patrickangeles]

Related #7859

[mattschumpert]

To be specific, @patrickangeles confirmed via rpk that this property was not showing up when you do

rpk topic describe -a foo

[mattschumpert]

@twmb any ideas here? @mmaslankaprv should't every property always be part of the topic metadata?

[daisukebe]

Just a side node: even we decide to not expose the read replica related flags via describe_configs, it'd be greatly helpful if there's a way to figure out all current topic properties, e.g. say via an admin api.

[vuldin]

Related to this issue is that redpanda.remote.read and redpanda.remote.write do appear, and for a read replica topic their values are both true. This is problematic though, since it doesn't make sense for a read replica topic to have remote.write set to true. Not only do users not see readreplica, but they also see incorrect values.

[KiaRaghavan]

thanks @vuldin for documenting the issues with the read replica config values in topic describe

[github-actions]

This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

[github-actions]

This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.