[BUG] V6.0 pushes API with empty serviceUrl

Open
#670 4 comments 2 reactions 1 assignee View on GitHub

@guythetechie is already working on this.

Since Sep 18, 2024.

Assessment

This issue has not been assessed yet.

Description

Release version

v6.0.11

Describe the bug

APIOps removes the serviceUrl (also known as HTTP(s) Endpoint) configuration for some of our APIs.
the serviceUrl is overwritten for every environment in a configuration and a couple (that we have seen) of our APIs had the serviceUrl changed to null by APIOps after upgrading to v6.0.11

I just rolled back to v5 and the few API have got their serviceUrl back

Expected behavior

API consistently deployed with serviceUrl if it is overwritten from configuration file

Actual behavior

few API deploy with serviceUrl as null

Reproduction Steps

The apiInformation, specs and config file did not change since v5 for those API so I am unsure why it would fail here.

apiInformation.json:

{
  "properties": {
    "apiRevision": "1",
    "authenticationSettings": {},
    "displayName": "rp-sis",
    "isCurrent": true,
    "path": "rp/scheme-integration-service",
    "protocols": ["https"],
    "serviceUrl": "https://sis.example.net",
    "subscriptionRequired": false
  }
}

configuration.d1.yml:

---
apimServiceName: apimxxxxx
[...]
apis:
[...]
  - name: rp-sis
    properties:
      serviceUrl: "https://sis.dev-example.net"
[...]
Dominant language
C#
Stars
448
Forks
247
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.