Skip to content

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

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions