[Question]-Issue: Named Values not overridden via configuration.prod.yaml in APIOps Publisher
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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
- 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: ->
- Backend-based API Example
- For another API:
- Backend created -> gender-url = https://genderize.io
- Policy ->
- Extractor Output
After running extractor pipeline:
- Policy correctly contains ->
- Backend reference also extracted correctly
- 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"
- 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
- 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
-
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 -
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?
- What is the correct structure or required flags?
Actual behavior
- 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
- 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?
- What is the correct structure or required flags?
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·