Unnecessary fields for a particular option should not be added by cli at initialization

[Aniruddh25]

Do you observe key-fields property (with empty array as the value) being added by CLI even if the source type is a stored procedure?
I think this should only be added if its view as mandated by the schema. Please create a bug if that's the case.

[Aniruddh25]

Ensure the config created for cli is valid with respect to the json schema.

[severussundar]

We are not seeing empty array for key-fields in case for stored procedures. The unit tests are updated to reflect this.

[Aniruddh25]

How about other options - not only for this particular scenario. The issue is more about ensuring CLI generates a config that adheres to our own published schema

[abhishekkumams]

I checked the below:

1. created table without key-fields, key-fields was not present in config.
2. created views without key-fields, key-fields was not present in config.
3. converted table/view with key fields to Stored procedure, key-fields was not present in config.

I'll check if there are any other fields which are unnecessary but still show up in the config.

[abhishekkumams]

Closing this issue, as it has been verified that this issue is no longer happening.