Skip to content

[release/9.0] Remove OneLoc PAT dependencies - #17457

Open
missymessa wants to merge 4 commits into
dotnet:release/9.0from
missymessa:missymessa/oneloc-pat-fallback-cleanup-release-9.0
Open

[release/9.0] Remove OneLoc PAT dependencies#17457
missymessa wants to merge 4 commits into
dotnet:release/9.0from
missymessa:missymessa/oneloc-pat-fallback-cleanup-release-9.0

Conversation

@missymessa

@missymessa missymessa commented Aug 31, 2026

Copy link
Copy Markdown
Member

Summary

  • backport complete removal of the OneLocBuildVariables variable group to release/9.0
  • remove the Ceapex and GitHub PAT parameters and all fallback paths
  • require short-lived Ceapex WIF and GitHub App tokens in the provisioned projects
  • update the OneLoc authentication documentation

Backport of the main cleanup for AB#10151 and AB#12331.

Import the legacy variable group only when the Ceapex or GitHub PAT fallback can be selected.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: bc4e1c74-f3b4-4965-932e-5e63cff7e877
@missymessa
missymessa requested review from mmitche and a lite review from Copilot August 31, 2026 16:11

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Pull request overview

This PR backports the OneLoc legacy variable-group cleanup to release/9.0 by conditionally attaching the OneLocBuildVariables group only when PAT-based fallback auth can be used, avoiding unnecessary legacy PAT hydration when both Ceapex WIF and GitHub App credentials are selected.

Changes:

  • Gate OneLocBuildVariables variable group attachment behind a template expression that detects when Ceapex PAT or GitHub PAT fallback may be needed.
  • Preserve legacy PAT availability for non-internal/DevDiv projects and for opt-out/unsupported GitHub App scenarios.
File summaries
File Description
eng/common/core-templates/job/onelocbuild.yml Conditionally includes the legacy OneLoc variable group only when PAT fallback paths are possible, reducing unnecessary secret downloads.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Copilot AI review requested due to automatic review settings September 1, 2026 00:12

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0 new
  • Review effort level: Lite

@missymessa
missymessa enabled auto-merge (squash) September 1, 2026 13:29
@missymessa

Copy link
Copy Markdown
Member Author

@mmitche please take a look!

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings September 3, 2026 20:04
@missymessa missymessa changed the title [release/9.0] Avoid downloading unused OneLoc PATs [release/9.0] Remove OneLoc PAT dependencies Sep 3, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The new project-scope guard uses a non-standard template expression function spelling (notIn) that deviates from established repo usage and could cause template evaluation failures.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details
  • Files reviewed: 3/3 changed files
  • Comments generated: 1
  • Review effort level: Lite

steps:
- ${{ if eq(parameters.is1ESPipeline, '') }}:
- 'Illegal entry point, is1ESPipeline is not defined. Repository yaml should not directly reference templates in core-templates folder.': error
- ${{ if notIn(variables['System.TeamProject'], 'internal', 'DevDiv') }}:
Copilot AI review requested due to automatic review settings September 3, 2026 20:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The updated template uses an unsupported notIn(...) Azure Pipelines template-expression function, which will break template expansion until corrected.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details
  • Files reviewed: 3/3 changed files
  • Comments generated: 1
  • Review effort level: Lite

steps:
- ${{ if eq(parameters.is1ESPipeline, '') }}:
- 'Illegal entry point, is1ESPipeline is not defined. Repository yaml should not directly reference templates in core-templates folder.': error
- ${{ if notIn(variables['System.TeamProject'], 'internal', 'DevDiv') }}:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants