Skip to content

chore: Reoslve Conflict#131

Open
NirajC-Microsoft wants to merge 1 commit intodevfrom
psl-resolve-conflict
Open

chore: Reoslve Conflict#131
NirajC-Microsoft wants to merge 1 commit intodevfrom
psl-resolve-conflict

Conversation

@NirajC-Microsoft
Copy link
Contributor

Purpose

This pull request updates several GitHub Actions workflow files to improve security, standardize Azure authentication, and simplify deployment configuration. The main changes include switching from manual Azure CLI login to the azure/login@v2 action, removing redundant secrets, consolidating Linux and Windows deployment workflows, and adding support for dynamic runner selection.

Authentication and Security Improvements

  • Switched Azure authentication from manual CLI login to the official azure/login@v2 GitHub Action in .github/workflows/ci.yml, .github/workflows/docker-build-and-push.yml, and other workflows, making authentication more secure and maintainable. [1] [2] [3]
  • Added id-token: write permission to workflows to support OIDC-based authentication for Azure, improving security posture. [1] [2] [3]

Workflow Configuration and Environment Standardization

  • Set environment: production for key jobs in CI, Docker build, and cleanup workflows to ensure consistent environment context for deployments. [1] [2] [3] [4]
  • Removed unnecessary manual secret references for Azure Container Registry login, replacing them with Azure CLI login via the workflow.

Deployment Workflow Simplification

  • Consolidated Linux and Windows deployment workflows by removing .github/workflows/deploy-windows.yml and renaming .github/workflows/deploy-linux.yml to .github/workflows/deploy-v2.yml, streamlining deployment logic. [1] [2]
  • Added a runner_os input to the deployment workflow, allowing dynamic selection between ubuntu-latest and windows-latest runners based on user input, and propagated this through workflow outputs and orchestrator calls. [1] [2] [3] [4] [5] [6]

Workflow Permissions Cleanup

  • Removed redundant permissions blocks from workflow orchestrator and cleanup jobs, relying on centralized permissions management. [1] [2]

These updates make the workflows more secure, flexible, and easier to maintain, particularly around Azure authentication and deployment environment selection.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

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.

1 participant