Today, we maintain two separate flows—one for dev and one for prod—because each Kafka cluster requires a different number of partitions. This means developers need to enter the topic name twice, which creates opportunities for typos and generally leads to frustration. What we would like to achieve is a single flow where the user builds an object that looks something like: { "kafka-dev": 5, "kafka-prod": 10 } What we want from the UI: 1. The keys should be selected from an entity picker, where the entities are our Kafka clusters registered in the IDP in this example. 2. The value should be a number field for partitions in this example. 3. Once the user selects an entity (e.g., kafka-dev), it should no longer appear in the next entity picker—essentially preventing duplicate selections. 4. The user should be able to add multiple cluster → partition entries dynamically (similar to “add item” behavior in forms). We’ve implemented something similar using Backstage, and we’re hoping to recreate this experience in Port.
