Across the platform UI, we have configuration properties sections that are immediately drawn with a single row for key and value. For some screens like connections, the configuration properties fields can be left empty, and submission of the form validates without failure. But then other screens like creating a destination, if the key and value row that is immediately rendered are left blank, the validation fails.

We ideally should present a unified approach across our screens.

We should decide if we think there is value in showing the empty row in the first place. I would argue in some contexts, it's unnecessary, like when creating a Kafka connection where all you need to specify are the broker host/port values. But then I can see in other places like when you define a source or destination, they may make more sense.

My humble opinion is that we should refrain from adding the row by default, and if the context demands configuration properties, the user presses the add property button. This avoids the confusion on whether the row must or does not need to be deleted if configuration properties are not mandatory.