Skip to content

Remove legacy GitHub auth args from ELM migrations create (device flow only) - #1512

Merged
mishrarish merged 4 commits into
Azure:masterfrom
bhuvanshahMSFT:elm-remove-service-connection-auth
Aug 12, 2026
Merged

Remove legacy GitHub auth args from ELM migrations create (device flow only)#1512
mishrarish merged 4 commits into
Azure:masterfrom
bhuvanshahMSFT:elm-remove-service-connection-auth

Conversation

@bhuvanshahMSFT

Copy link
Copy Markdown
Contributor

Makes interactive GitHub device flow the only auth path for az devops migrations create.

Changes:

  • Remove --service-endpoint-id and --github-token / ELM_GITHUB_TOKEN args. The server now supports third-party app auth, so the CLI resolves the GitHub user token via interactive device flow only.
  • Keep --pipeline-service-connection-id (unchanged).

Testing:

  • 102 unit tests pass in test_migration.py.
  • Validated end-to-end against production (validate-only migration mseng/1ES → msft.ghe.com/1ES); server resolved the target owner from the device-flow token, no service connection required.

Demo User added 4 commits August 10, 2026 13:27
…reate (device flow only)

The server now supports third-party app auth (Git.EnterpriseLiveMigration.EnableThirdPartyAppAuth), so GitHub authentication for 'az devops migrations create' is handled entirely via interactive device flow.

- Remove --service-endpoint-id and --github-token args (and ELM_GITHUB_TOKEN env var)

- Device flow is now the only GitHub auth path; token is resolved from device flow and sent as gitHubUserToken

- Update help text, examples, and unit tests accordingly
Remove --github-token / ELM_GITHUB_TOKEN / --service-endpoint-id references from ELM docs; document interactive device flow as the sole GitHub auth path.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

LGTM

@mishrarish
mishrarish merged commit 9ae4396 into Azure:master Aug 12, 2026
21 checks passed
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.

3 participants