We have a tool which runs topicctl bootstrap, then topicctl rebalance in succession.
With this approach we are currently unable to rebalance topics such as __consumer_offsets since they are explicitly not considered for bootstrap
This change will introduce a new flag which allows us to bootstrap these topic configurations.
The default will be to continue current behavior of skipping double-underscore topics.
Example usage
topicctl bootstrap --cluster-config=... --allow-internal-topics=true --output=./topics/
[2024-05-10 17:26:47] INFO Writing config to topics/__amazon_msk_canary.yaml
[2024-05-10 17:26:47] INFO Writing config to topics/__consumer_offsets.yaml
[2024-05-10 17:26:47] INFO Writing config to topics/__strimzi-topic-operator-kstreams-topic-store-changelog.yaml
[2024-05-10 17:26:47] INFO Writing config to topics/__strimzi_store_topic.yaml
[2024-05-10 17:26:47] INFO Skipping over existing config topics/mp-events-userid.yaml
topicctl bootstrap, thentopicctl rebalancein succession.__consumer_offsetssince they are explicitly not considered for bootstrapExample usage