Refactor e2e Federated Credentials test to use a stable repository

[Copilot]

❔What, Why & How

The FederatedCredentials e2e test was refactored to use a stable repository (e2e-bingmaps.appsource) instead of deleting and recreating it on each run. Federated credentials require stable repository identity to function correctly.

Changes:

• Added helper functions to e2eTests/e2eTestHelper.psm1:

  • CleanupWorkflowRuns: Deletes all workflow runs in a repository to ensure clean state for testing
  • ResetRepositoryToSource: Resets a repository to match a source repository via git reset --hard and force push, preserving repository identity
  • Both functions include comprehensive PowerShell comment-based help documentation

• Modified test flow in e2eTests/scenarios/FederatedCredentials/runtest.ps1:

  • Test now requires e2e-bingmaps.appsource repository to exist before running (throws error if missing)
  • Repository is reset to match bcsamples-bingmaps.appsource for deterministic state
  • Workflow runs are cleaned up before triggering new ones
  • Repository settings are re-applied after reset
  • Fixed workflow tracking to wait for correct CI/CD run based on timestamps

• Repository naming:

  • Changed from tmp-bingmaps.appsource to e2e-bingmaps.appsource to avoid automatic deletion by cleanup scripts (which target tmp* pattern)

• Fixed "unknown flag: --quiet" error:

  • Removed -- --quiet from invoke-gh repo clone calls (gh doesn't properly handle this flag)
  • Git commands with --quiet (fetch, checkout, reset, push, commit) are unaffected and continue to work correctly

• Code quality:

  • Removed all trailing whitespaces
  • Made parameters mandatory where appropriate
  • Added comprehensive error handling with LASTEXITCODE checks

Before:

invoke-gh repo clone $repository . -- --quiet

After:

invoke-gh repo clone $repository .

✅ Checklist

• Add tests (E2E, unit tests)
• Update RELEASENOTES.md
• Update documentation (e.g. for new settings or scenarios)
• Add telemetry

Original prompt

Refactor the FederatedCredentials end-to-end test scenario in microsoft/AL-Go so it reuses an existing temporary repository instead of deleting and recreating it on every run. The current approach creates a new repository called tmp-bingmaps.appsource copied from microsoft/bcsamples-bingmaps.appsource. Federated credentials no longer work with repository name-based matching, so the repository must be stable across runs.

Context:

• Failing job URL: https://github.com/microsoft/AL-Go/actions/runs/21470716621/job/61842467415
• Failure occurs when the test triggers the "Update AL-Go System Files" workflow in the newly created repository.
• The test script is at e2eTests/scenarios/FederatedCredentials/runtest.ps1 and currently:
  • checks if the temp repo exists
  • deletes it if it exists
  • recreates it from template
  • then runs Update AL-Go System Files

Required changes:

1. Modify e2eTests/scenarios/FederatedCredentials/runtest.ps1 to reuse the repo if it already exists.
   • Do not delete the repo anymore.
   • If the repo exists, reset it to match the source repo (microsoft/bcsamples-bingmaps.appsource) in a deterministic way.
   • Ensure the repo ends up with the same default branch content expected by the scenario (main).
2. Add cleanup logic for workflow runs in the reused temp repo to prevent the run list from growing and to ensure the subsequent WaitWorkflow logic targets the correct run.
   • Before starting the scenario, delete older workflow runs (keep a small number like the last 5-10), or alternatively capture the run id of the workflow triggered and wait specifically for that.
3. Ensure secrets and settings required for the test are still present/updated.
   • The script sets Azure_Credentials; preserve this.
   • The script passes addRepoSettings for ghTokenWorkflowSecretName; ensure this still works if repo already exists.
4. Update any helper functions or supporting scripts if needed to support resetting repo contents and cleaning workflow runs.

Acceptance criteria:

• The test no longer relies on deleting/recreating tmp-bingmaps.appsource.
• The temp repo is stable across runs and compatible with federated credentials.
• The script reliably waits for and inspects the workflow run it triggered, not an older run.
• Add clear comments explaining why the repo is reused.

Relevant files:

• e2eTests/scenarios/FederatedCredentials/runtest.ps1
• e2eTests/Workflows/RunUpdateAlGoSystemFiles.ps1 (workflow trigger helper)
• Any relevant helper module under e2eTests/e2eTestHelper.psm1 if needed.

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mazhelez]

Good work!

@copilot the following script is used in a workflow to clean up temp repositories: "Internal\Scripts\RemoveTempRepos.ps1"
Can you adjust the script or rename the repository, so that it doesn't get deleted?

[Copilot]

Good work!

@copilot the following script is used in a workflow to clean up temp repositories: "Internal\Scripts\RemoveTempRepos.ps1"...

Done. Updated Internal/Scripts/RemoveTempRepos.ps1 to exclude tmp-bingmaps.appsource from automatic deletion. The repository will now remain stable across cleanup operations. Commit: 2309402

[mazhelez]

Getting there.

@copilot can you please also remove trailing whitespaces?

[Copilot]

Getting there.

@copilot can you please also remove trailing whitespaces?

Done. Removed trailing whitespaces from runtest.ps1 (lines 131-132). Commit: 626a791

[mazhelez]

@copilot can you please resolve the merge conflicts?

[Copilot]

@copilot can you please resolve the merge conflicts?

Done. Resolved merge conflicts by taking the updated base from main branch and re-adding our two helper functions (CleanupWorkflowRuns and ResetRepositoryToSource) at lines 345 and 397 respectively. Commit: 44d1b6c