Kong / Kong/kubernetes-testing-framework
E2E tests should take into account whether GKE related secrets are present besides PULP_PASSWORD
- Dominant language
- Go
- Stars
- 44
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
#538 introduced e2e tests that are run when `PULP_PASSWORD` (needed to get a license) is present. What it didn't take into account is the fact that `GOOGLE_APPLICATION_CREDENTIALS`, `GOOGLE_PROJECT` and `GOOGLE_LOCATION`.
And in case of dependabot's PRs, those are not present, e.g. https://github.com/Kong/kubernetes-testing-framework/pull/546
### Expected Behavior
E2E tests do not fail for dependabot's PRs.
### Steps To Reproduce
_No response_
### Kong Kubernetes Testing Framework Version
_No response_
### Kubernetes version
_No response_
### Anything else?
_No response_
Contributor guide
Research direction
Start by reviewing the E2E test trigger introduced in #538 and compare it with dependabot's PR #546. Check how PULP_PASSWORD, GOOGLE_APPLICATION_CREDENTIALS, GOOGLE_PROJECT, and GOOGLE_LOCATION are evaluated, then verify that E2E tests are skipped when the required GKE-related secrets are absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud, kubernetes
- Domain
- ci-cd, cloud, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100