[BUG] Workspace Publisher YAML File overload variables ignored

Open

#758 opened on May 16, 2025 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: azure, csharp, yaml
Domain: api, cloud

Research direction

Start with the Workspace extraction and the sample Publisher Configuration YAML described in the reproduction steps, then compare its exported variables with the values used during destination APIM deployment. Done means identifying the required overload keys and confirming that namedValues and serviceUrls are applied instead of source APIM values.

Written by the indexing model from the issue text.

Description

Release version

v6.0.0.2-alpha.1.0.3

Describe the bug

Hello team,

Can we get a sample publisher file for workspace configuration publishing?

I've been trying for the last couple of hours to overload namedValues or serviceUrls of the APIs inside the Workspaces, but to no success.

The regular sample YAML publisher file seems to not apply for Workspaces scenarios and the values inside of it are ignored by the publisher tool. What keys should we use within it to make the publisher tool aware of the values that need overloading?

Thank you!

Expected behavior

YAML Publisher configuration values are not ignored on APIM and the destination APIM is updated with the correct values

Actual behavior

The APIs and NamedValues get deployed in the Workspace with the values extracted from source APIM.

Reproduction Steps

Using the Workspace supported ApiOps Toolkit extract a Workspace.

Try to overload the exported variables with the sample provided Publisher Configuration YAML

Dominant language: C#
Stars: 448
Forks: 247
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.

Similar issues

[quality-improver] Repository Quality: AzureFoundry Extension Missing from Self-Registration Acceptance Test Open

type/automation type/tech-debt

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

microsoft/testfx#11431 · Opened Sep 21, 2026
[Bug]: Composite `ui screenshot` success output ignores `--quiet` Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

microsoft/winappCli#914 · Opened Sep 21, 2026
GeometryHelper.FlattenArc / FlattenCubicBezier / FlattenQuadraticBezier emit a NaN point when the segment count truncates to 0 (0/0) — a Path with a sub-pixel arc fail-fasts Windows with D2DERR_BAD_NUMBER (root cause of #8512, #13757) Open

t/bug

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

dotnet/maui#38751 · 1 reaction · Opened Sep 21, 2026
[CI Failure] Flaky: MauiBuildQueueTests.CancelQueuedResource_CompletesGracefullyAndDoesNotAcquireSemaphore asserts exact exception type but sometimes gets TaskCanceledException instead of OperationCanceledException Open

ci-failure-cause test-failure

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

microsoft/aspire#20284 · Opened Sep 21, 2026
The login flow's text-link submit is 42 px tall on a narrow screen; its docblock says 44 Open

area:auth FE mvp P3

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

klasolsson81/jobbliggaren#1788 · Opened Sep 21, 2026

More C# issues