[BUG] APINames are not extracted
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by reproducing the issue with the provided workspaceNames, apiNames, and related configuration, then compare the debug traces for the two configurations. Done means the API selected by apiNames is written to its expected artifact file rather than only appearing in the trace.
Written by the indexing model from the issue text.
Description
Release version
v6.0.1.4
Describe the bug
The API is displayed in the log (trace) but is not written to a file. Everything else is extracted correctly.
Strangely, it works with the following configuration, but i don't need extractAll.
JSON is displayed there.
Expected behavior
Extract API with apiNames: value
Actual behavior
Extract api with apiNames value not possible
Reproduction Steps
workspaceNames:
- ignore
apiNames:
- myAPIName
backendNames:
- myBackendName
diagnosticNames:
#- ignore
loggerNames:
#- ignore
namedValueNames:
#- ignore
productNames:
#- ignore
subscriptionNames:
- mySubscriptionName
tagNames:
#- ignore
policyFragmentNames:
#- ignore
versionSetNames:
#- ignore
Debug Trace ends like this:
info: extractor[0]
Writing API operation policy file /home/vsts/work/1/artifacts-from-portal/sharedproducts/apim/apimArtifacts/apis/myAPIName/operations/post-action/policy.xml...
dbug: Microsoft.FeatureManagement.FeatureManager[0]
This configuration doesn't extract apiNames:
workspaceNames:
- ignore
apiNames:
- myAPIName
backendNames:
- myBackendName
diagnosticNames:
- ignore
loggerNames:
- ignore
namedValueNames:
- myNamedValues
productNames:
- rfmint
subscriptionNames:
- mySubscriptionName
tagNames:
- ignore
policyFragmentNames:
- ignore
versionSetNames:
- ignore
Debug Trace ends like this:
dbug: Microsoft.FeatureManagement.FeatureManager[0]
The feature definition for the feature 'Workspaces' was not found.
info: extractor[0]
The write is simply missing here, although the API or the content for the
- 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 ·