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

Fixes how upstream-authority-ejbca integration test calls kubectl and helm #5613

Merged

Conversation

nweisenauer-sap
Copy link
Contributor

Pull Request check list

  • [ x ] Commit conforms to CONTRIBUTING.md?
  • [ / ] Proper tests/regressions included?
  • [ / ] Documentation updated?

Affected functionality
upstream-authority-ejbca test now calls the binaries from the ./bin folder

Description of change
On our runners, the new integration test upstream-authority-ejbca fails, complaining that helm and kubectl are not preinstalled. However, this test, similar to the upstream-authority-cert-manager, downloads these tools beforehand (inside the 00-setup-kind script). The issue is that the script downloads these tools to the ./bin folder, which is fine, but the test itself does mixed calls of kubectl, sometimes using kubectl, sometimes ./bin/kubectl. Also, the prerequisite checks do not check for the ./bin folder.
Which issue this PR fixes

00-setup-kind downloads kubectl, helm and kind to ./bin folder
upstream-authority-ejbca test now calls the binaries from this prepared bin folder

Signed-off-by: Nico Weisenauer <[email protected]>
Signed-off-by: Nico Weisenauer <[email protected]>
@amartinezfayo amartinezfayo self-assigned this Oct 31, 2024
Copy link
Member

@amartinezfayo amartinezfayo left a comment

Choose a reason for hiding this comment

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

Thank you @nweisenauer-sap!

@amartinezfayo amartinezfayo merged commit a8857ba into spiffe:main Nov 8, 2024
34 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.

2 participants