kata-containers/tests/functional
Aurélien Bombo 9dd3807467 ci: Use OIDC to log into Azure
This completely eliminates the Azure secret from the repo, following the below
guidance:

https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-azure

The federated identity is scoped to the `ci` environment, meaning:

 * I had to specify this environment in some YAMLs. I don't believe there's any
   downside to this.
 * As previously, the CI works seamlessly both from PRs and in the manual
   workflow.

I also deleted the tools/packaging/kata-deploy/action folder as it doesn't seem
to be used anymore, and it contains a reference to the secret.

Signed-off-by: Aurélien Bombo <abombo@microsoft.com>
2025-06-06 15:26:10 -05:00
..
kata-agent-apis agent-ctl: Add support to test kata-agent's container creation APIs. 2024-11-01 22:18:54 +05:30
kata-deploy ci: Use OIDC to log into Azure 2025-06-06 15:26:10 -05:00
kata-monitor CI: change the containerd tarball name to containerd 2025-01-07 17:39:05 +08:00
tracing shellcheck: Fix shellcheck SC2145 2025-03-04 09:35:46 +00:00
vfio test: vfio: Attempt to fix logic 2025-03-04 09:39:10 +00:00
vfio-ap shellcheck: Fix shellcheck SC2068 2025-03-04 09:35:46 +00:00