[Question] How to define so that an API is only available on a Self Hosted Gateway (and not on 'Managed') ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the extractor tool and compare the extracted API configuration with the API's gateways property after publishing. Trace how gateway assignments are read and applied, then verify that an API extracted without Managed remains unavailable on Managed after republishing.
Written by the indexing model from the issue text.
Description
Release version
APIOps Toolkit for Azure APIM v6.0.1.3
Question Details
How can I define that an API should only be available on a Self Hosted Gateway and not on 'Managed' ?
In the AZure Portal API Management UI this is done by removing 'Managed' in the gateways property.
Expected behavior
I would like to have the possibilty to 'deny' availability on 'Managed'
Actual behavior
When a new API is created via APIOps, 'Managed' is always included in the 'gateways' property in the 'Azure Portal API Management UI' API Settings
Reproduction Steps
- Create an API in the 'Azure Portal API Management UI'
- Remove 'Managed' from the 'gateways' property in the 'Azure Portal API Management UI' (API > Settings tab)
- Extract the API Management configuration with the 'extractor' tool
- Delete the API in the 'Azure Portal API Management UI'
- Publish the extracted API Management configuration from Step 3
- Check the 'gateways' property in the 'Azure Portal API Management UI' (API > Settings tab), it will have 'Managed' which is not wanted
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RayWangQvQ/BiliBiliToolPro#1137 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100