Maintaining the assumption that functionality to delete topics won't be added, it'd still be ideal if we had a means to facilitate operational tasks such as cleaning up old resources. If we are needing to manually delete topics, it'd be great if there was a way to get a list of topics that are present in the cluster but don't have a corresponding local configuration file.
The ask: To add an argument or functionality to the get topics command to list "orphaned" topics that. (eg. topicctl get topics --list-topics-missing-config)
Optional ask: Add a list of topics to be listed from output (eg. system topics) to enable further automations?