I see that you guys justify the requirement to delete and recreate a custom api when the swagger file changes appropriates the infamous "by design" dev loophole.
since you don't justify the justification anywhere in documentation, i can only surmise that you think changing a swagger file is like changing regular apis. if this is the case, then your draconian assumption that the swagger changes are always breaking changes seems...well, draconian.
so please, do two things:
- document this "feature" of powerapps, and do it clearly. (you understand, don't you, that all your customers are powerapps rookies trying to learn by trial and error how to thrive in this brave new world of software development you offer us. forcing us to start from scratch with each thing we learn will not endear you to your customers.)
- do a much better job convincing us there is something peculiar to powerapps custom apis that warrants the "by design" designation.
Please check out these two articles and let us know if these help to clarify your ask:
https://powerapps.microsoft.com/en-us/tutorials/register-custom-api/
https://powerapps.microsoft.com/en-us/tutorials/customapi-how-to-swagger/
https://powerapps.microsoft.com/en-us/blog/custom-api-with-authentication/
Thank you again for your feedback and suggestions!