jetstack / jetstack/jetstack-secure-gcm
Edit the smoke test of the Google CAS issuer so that it properly tests the CAS issuer
- Dominant language
- Mustache
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
In #5, I decided to only smoke test cert-manager itself as opposed to testing both cert-manager and google-cas-issuer.
Today, I discovered that the testrunner that we use for the smoke tests has a "GCP runtime config" support built-in. [Google Cloud Runtime Config](https://cloud.google.com/sdk/gcloud/reference/beta/runtime-config/configs) could allow us to create the necessary GCP serviceaccount and bindings required for the CAS issuer smoke test.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the existing smoke-test setup and the decision recorded in #5, then inspect the testrunner's GCP runtime config support. The work is complete when the smoke test exercises google-cas-issuer as well as cert-manager using the required GCP service account and bindings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud
- Domain
- cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100