[BUG] Publisher not throwing error in GA workflows when connectivity is not available
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the deployment with an API named value backed by an inaccessible Azure Key Vault, comparing the GA and ADO publisher paths. Trace named-value creation and error handling in the publisher workflow. Done means GA reports the Key Vault access failure and stops before attempting dependent policy setup.
Written by the indexing model from the issue text.
Description
Release version
v6.0.1.1
Describe the bug
When publisher run for the artifacts having named values attached to Azure Keyvault, during publisher run if AKV is not accessible or have no proper rights ADO throws an error clearly stating the same but GA doesn't fail and go ahead without any error.
Expected behavior
GA also should fail when there is no Access to the respective resource like ADO does.
Actual behavior
GA does not fail when connectivity is not available and logs says it has put the named values in APIM but actually it is not created. At the same time ADO works fine and give proper error.
Reproduction Steps
- Create an api has reference to namedvalue which holds the value from the Keyvault.
- Deploy to another instance which does not have access to the Kwyvault.
- Run publisher.
- In GA you can see it will not fail for the named value but fail when it will try to setup the policy as named value object is not created and it is trying to refer the same. And when you run the same using ADO it will fail at the stage of named value creation itself.
- 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 3/5 1-2 days Newbie friendliness 70/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
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·