Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] API not present in configuration file is still being deployed

Open
#659 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
api, devops

Research direction

Start by examining how configuration.d1.yaml is parsed and how the deployment process selects folders under apis. Compare the explicitly listed api1 entry with the unlisted api2 folder, including apiInformation.json and specification.json. Done means an API omitted or commented out of the configuration is not deployed while listed APIs still are.

Written by the indexing model from the issue text.

Description

Release version

v6.0.11

Describe the bug

As per documentation and #435, I was told that I should be able to prevent the deployment of an API by omitting the API from the configuration file.

However, this does not appear to work as I have an API currently commented in configuration code:

[...]
apis:
[...]
  # - name: api2
  #   properties:
  #     serviceUrl: ""
  # there is no dev env

but the API is being deployed whether I make a publish all artifacts or edit the specs and publish last commit...
I always deploy with configuration file as I have multiple environment, I am using different configuration files for each environment

Expected behavior

Only API defined explicitly in the configuration files are published. API that are commented should not be published.

Actual behavior

All API are deployed, all the time.

Reproduction Steps

configuration file configuration.d1.yaml:

---
apimServiceName: apimdev01
apis:
#APIs Begin
  - name: api1
    properties:
      serviceUrl: "https://api1.example.net"
  # - name: api2
  #   properties:
  #     serviceUrl: ""
  # there is no dev env

folder structure:

  • apis
    • api1
      • apiInformation.json
      • specification.json
    • api2
      • apiInformation.json
      • specification.json
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.