Hi,
Wanted to know what would be the "best practice" when working with Custom connectors.
Our preference is to publish the custom connectors via API-M (since all APIs are managed by a seperate team).
But once the custom connector is in Dev, how do we take it to QA or PROD?
We can include the custom connector in a solution. But we would have to update the API end-point in QA and PROD post-deployment.
Wondering if that would cause any additional solution layers.
Any and all advice welcome! 🙂
TIA!
A secondary solution would be to use policies to set the URL, so you when you set up the connection for the connector you can set the url for it https://learn.microsoft.com/en-us/connectors/custom-connectors/policy-templates/dynamichosturl/dynamichosturl
When putting it inside a solution, I am unable to share it with other developers on my team. How do you get around this issue or does only one developer have access to your custom connector?