Integrations involving Azure API Management that utilize a custom domain
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the workflow through Platforms > Integrations > New Integration > From Azure API Management, then inspect the automatically created deployment and compare it with a manually created deployment. Done means the custom API Management domain is used automatically or the runtime URL can be edited afterward, with the built-in hostname no longer forced.
Written by the indexing model from the issue text.
Description
Description
When integrating API Center with an API Management Service that uses a custom domain, a new deployment is created automatically. However, it will use the APIM built-in Gateway hostname .azure-api.net instead of the custom domain. There is currently no way to change this.
Reproduction steps
Steps to reproduce the behavior:
- Create a new integration in API Center
- Platforms
- Integrations
- New Integration
- From Azure API Management
Complete the wizard
- Go to Deployments and locate the deployment that was created. Check the Deployment Runtime, and you'll see .azure-api.net/ as the base URL, which cannot be changed to a custom domain. In the API Center Portal, the built-in hostname will also appear.
Expected behavior
The intended functionality is for the custom domain set in API Management to be automatically used for deployments created during new integration setups, or at minimum, to provide an option to manually edit the runtime URL afterwards.
Actual behavior
The current behavior is that the field is greyed out only for Deployments created automatically when a new integration is set up, and it cannot be changed. However, for Deployments created manually, this field remains enabled.
- Dominant language
- PowerShell
- Stars
- 45
- Forks
- 21
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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/api-center
-
Feature request Untriaged
Difficulty 5/5 Over a week Newbie friendliness 48/100
Azure/api-center#93 · 1 comment ·
-
Bug Untriaged
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/api-center#92 · 1 reaction ·
-
Bug Untriaged
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Azure/api-center#91 · 1 comment ·
-
Feature request Untriaged
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Azure/api-center#90 · 1 comment · 1 reaction ·
-
Bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Azure/api-center#89 · 1 comment · 1 reaction ·
All issues in Azure/api-center
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#165 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100