[Question]-Issue: Named Values not overridden via configuration.prod.yaml in APIOps Publisher

Open
#845 4 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
Needs clarification
Activity status
Quiet
Tech stack
azure
Domain
api, cloud

Research direction

Start with configuration.prod.yaml and compare how the publisher applies the namedValues and backends sections. Trace the extractor and publisher pipeline using the reported agify-url and gender-url examples; done means either the named value is set to https://prod-agify.io in Prod or the supported environment-specific approach is documented.

Written by the indexing model from the issue text.

Description

Release version

v7.0.0-alpha.3.0.1

Question Details

Description :-
I am using APIOps to promote APIs from a Dev APIM instance to a Prod APIM instance across different resource groups (same tenant).
While backends are correctly overridden using configuration.prod.yaml, named values are NOT getting overridden and retain Dev values in Prod.

Environment :-

  • APIOps Version: v7.0.0-alpha.3.0.1
  • APIM Instances:
    • Dev: dev-apim-instance
    • Prod: prod-apim-instance
      Both resource groups have proper Contributor access via service connections

Setup / Workflow

  1. API Onboarding in Dev APIM
  • APIs are created manually in Dev APIM
  • Web service URL is NOT added in API settings
  • Instead:
    • A Named Value is created -> "agify-url = https://agify.io"
    • API Policy uses: ->
  1. Backend-based API Example
  1. Extractor Output
    After running extractor pipeline:
  • Policy correctly contains ->
  • Backend reference also extracted correctly
  1. Publisher Configuration (configuration.prod.yaml)
    apimServiceName: prod-apim-instance
    namedValues:

backends:

  1. Actual Behavior
  • Backend (gender-url) is correctly overridden in Prod
  • Named Value (agify-url) is NOT overridden
Expected behavior
  1. Expected Behavior
  • Named Values defined in configuration.prod.yaml should override values in Prod APIM
  • Final expected value in Prod -> agify-url = https://prod-agify.io
  1. Key Observation
    Backend override works
    Named Value override does NOT
    This suggests:
    Either namedValues override is not supported / broken in this version
    Or additional configuration/flag is required

  2. Question

  • Is overriding Named Values via configuration..yaml supported in APIOps v7?
  • If yes:
    • What is the correct structure or required flags?
      If not:
    • What is the recommended approach for environment-specific Named Values?
Actual behavior
  1. Actual Behavior
  • Backend (gender-url) is correctly overridden in Prod
  • Named Value (agify-url) is NOT overridden
Reproduction Steps
  1. Question
  • Is overriding Named Values via configuration..yaml supported in APIOps v7?
  • If yes:
    • What is the correct structure or required flags?
      If not:
    • What is the recommended approach for environment-specific Named Values?
Dominant language
C#
Stars
448
Forks
247
PR merge metrics
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.