Closed QuickScoP3s closed 1 day ago
Thank you for opening this issue, we will look into it.
Apologies. I misunderstood the infrastructure setup of APIM: I thought a version set exists under an API, but I now discovered it exists above an api.
I'm now creating the version set first, and then importing the api on top.
Describe the bug
I'm trying to create a new api with versionsets using
az apim api import
The command fails with the following error:
The api does not exist yet, so obviously the versionset also does not, but I would expect it to create the version set in that case. Am I missing any parameters or information? Does this command not support creating version sets directly?
Related command
Errors
cli.azure.cli.core.azclierror: (ResourceNotFound) ApiVersionSet not found. Code: ResourceNotFound Message: ApiVersionSet not found. az_command_data_logger: (ResourceNotFound) ApiVersionSet not found. Code: ResourceNotFound Message: ApiVersionSet not found
Issue script & Debug output
Expected behavior
I expect the import command to create an api + version set if none exists
Environment Summary
azure-cli 2.64.0
core 2.64.0 telemetry 1.1.0
Extensions: arcdata 1.5.18
Dependencies: msal 1.30.0 azure-mgmt-resource 23.1.1
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe' Extensions directory 'C:\Users\wautw.azure\cliextensions'
Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb 6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date
Additional context
We've already been using this command for a while to import existing api's, but this is the first time trying to use it to create a new api...