Hello @Sheldon Lyttle , Thank you for reaching out. Can you please go through this documentation which mentions about restrictions and known issues for importing APIs? If this does not help resolve the issue can you please let us know how you are importing the API? Are you you importing it as an OpenAPI specification?
Cannot import this App Service due to existing wildcard operations in the API
I have published an REST API from Visual Studio 2019 to App Services, and am now trying to import the API into API Management to take advantage of some of the added features this service offers.
Unfortunately, each time I try and import the API it complains that "Cannot import this App Service due to existing wildcard operations in the API".
For the life of me, I can't figure out where this "wildcard operation" is. When I look at the definition through Swagger, everything seems to have a defined name and method, and all the parameters seem to be clearly defined.
I am not even sure what a wildcard operation is!
Can anyone help me resolve this?
Azure API Management
2 answers
Sort by: Most helpful
-
ChaitanyaNaykodi-MSFT 27,476 Reputation points Microsoft Employee Moderator
2021-04-06T03:05:50.153+00:00 -
Alan Helmick 0 Reputation points
2023-12-31T22:27:19.12+00:00 I am importing a specification from an existing app service. It's funny how it would take me less time to configure a Linux server to do these things than it does to get your varied components to recognize or work together. I've been trying for 2 days to get a simple 2 endpoint api to work and this wild card message has me lost. I built a fully functional python app service but getting it to connect with an API is murder. Here is the error I get:
Cannot import this App Service.
- Cannot import this App Service due to existing wildcard operations in the API
This gives me no resolution as to get the blank API and the App Service to work together. It would be easier for me just to install nginx and configure it as an Oauth API server than to get these components to work together. Is it ok if I just use a VM to host my API, so I don't have to waste all this time in management overhead?
So I go to create a NEW API for the fully functional app service and I get:
One or more fields contain incorrect values:
- Cannot create API '<my app service name>' with the same Path '' as API '<my new api>' unless it's a part of the same version set
So I made sure they were both on the same version but no help. (sigh)