OpenAPI Spec to Power Connection Form

[derek1ee]

Current, when creating a connection, the list of properties are hard-coded. Which means every time a new types of connection is added (e.g. new service that requires some additional properties, a new auth type for an existing service) in the side car, the extension code needs to be manually updated to match before the capability is available to end users.

Instead, we should explore if it may be possible to remove the hard coded logic in the extension code, e.g. via swagger definition. There are also extensions to the swagger spec to support dynamic values, if needed - e.g., based on the selection of auth type, different and additional properties can dynamically become required.

https://learn.microsoft.com/en-us/connectors/custom-connectors/openapi-extensions#use-dynamic-values