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

[acaryatanaya]

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: ->

2. Backend-based API Example

• For another API:
  • Backend created -> gender-url = https://genderize.io
  • Policy ->

3. Extractor Output
   After running extractor pipeline:

• Policy correctly contains ->
• Backend reference also extracted correctly

4. Publisher Configuration (configuration.prod.yaml)
   apimServiceName: prod-apim-instance
   namedValues:

• name: agify-url
  properties:
  displayName: agify-url
  value: "https://prod-agify.io"

backends:

• name: gender-url
  properties:
  url: "https://prod-genderize.io"

5. Actual Behavior

• Backend (gender-url) is correctly overridden in Prod
• Named Value (agify-url) is NOT overridden
  • It still retains Dev value (https://agify.io)

Expected behavior

6. 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

7. 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

8. 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

5. Actual Behavior

• Backend (gender-url) is correctly overridden in Prod
• Named Value (agify-url) is NOT overridden
  • It still retains Dev value (https://agify.io)

Reproduction Steps

8. 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?

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[guythetechie]

I think something broke your formatting, and I can't really parse your configuration. Regardless, named value overrides are supported. Couple of things to check:

• Here is a sample configuration file that shows named value overrides.
• When overriding your named value, make sure you specify the named value name, not the display name. You can find your named value name in artifacts/named values/{your-named-value-name}.

   namedValues:
     - name: **MUST BE NAMED VALUE NAME**
       properties:
         displayName: environment