Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: misc enhancements to the azure e2e test code #1394

Conversation

mkulke
Copy link
Contributor

@mkulke mkulke commented Sep 1, 2023

I've thrown those in a single PR, mostly because it's friday. We can untangle, if desired, ofc.

  • Remove option to pass secrets to test run

    since leakage of secrets in the CI is a risk and federated credentials work well on github actions we remove the option to pass a CLIENT_SECRET to a test run. Local runs can keep using cli auth.

  • Parallize the tests

    it will speed up a test run and is a valid test path. there are no dependencies between the test cases, so flakes due to this would imply a bug we want to be aware of.

    Later, when we add more tests, we probably want to increase the parallelism when invoking go test, since it'll use nproc by default but the tests are not cpu-bound.

  • There is a misnomer in the ssh key parameter.

  • There is no need to query the API for the rg name in the cloud asserter, since we have the name in all cases.

Successful test run here

- Remove option to pass secrets to test run

  since leakage of secrets in the CI is a risk and
  federated credentials work well on github actions we
  remove the option to pass a CLIENT_SECRET to a test
  run. Local runs can keep using cli auth.

- Parallize the tests

  it will speed up a test run and is a valid test path.
  there are no dependencies between the test cases, so
  flakes due to this would imply a bug we want to be
  aware of.

- There is a misnomer in the ssh key parameter.

- There is no need to query the API for the rg name in the
  cloud asserter, since we have the name in all cases.

Signed-off-by: Magnus Kulke <magnuskulke@microsoft.com>
@surajssd
Copy link
Member

@mkulke can you rebase on latest? This can be merged I guess.

@mkulke mkulke force-pushed the mkulke/misc-improvements-to-az-e2e-code branch from 26c917d to 853664e Compare September 27, 2023 13:50
Copy link
Contributor

@kartikjoshi21 kartikjoshi21 left a comment

Choose a reason for hiding this comment

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

Looks good. Thanks for the work @mkulke

@kartikjoshi21 kartikjoshi21 merged commit cc34a12 into confidential-containers:main Oct 3, 2023
17 checks passed
@mkulke mkulke deleted the mkulke/misc-improvements-to-az-e2e-code branch September 17, 2024 06:54
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