Run zenko tests in codespace + some cleanup of unused files#2324
Run zenko tests in codespace + some cleanup of unused files#2324SylvainSenechal wants to merge 2 commits intoimprovement/ZENKO-5180from
Conversation
| "ghcr.io/devcontainers/features/docker-in-docker": {}, | ||
| "ghcr.io/devcontainers/features/github-cli:1": {}, | ||
| "ghcr.io/devcontainers/features/node:1": {}, | ||
| "ghcr.io/devcontainers/features/python:1": {}, |
There was a problem hiding this comment.
Python is already available in the codespace, but some yarn install command because something "gyp" related to python failed to install. This should fix it
There was a problem hiding this comment.
Unrelated to running zenko tests in Codespace, but I did some decluttering in this pr and removed 4 unused files (removed docker entry point, and the associated files that werent used by anything else)
There was a problem hiding this comment.
This structure and usage is very similar to what I did for the Cucumber tests.
Tbh, I was also able to run the test without a pod, but it required port forward, and using different values for some variables, which later will probably become annoying because we don't want to have to deal with 2 values for the same variables depending on whether the test is running in github ci or codespace.
So maybe later we'll come back to this if we decide to run all tests outside of cluster, but don't really wanna deal with it for now
| TEST_GREP="${1:-should list objects in V2 format}" | ||
| TEST_PATH="${2:-cloudserver}" | ||
|
|
||
| ZENKO_ACCESS_KEY=$(kubectl get secret end2end-management-account-creds.v1 -o jsonpath='{.data.accessKey}' | base64 -d) |
There was a problem hiding this comment.
These env variables will eventually be removed (calculated automatically from within the test)
SylvainSenechal
force-pushed
the
improvement/ZENKO-5180
branch
12 times, most recently
from
59e3b03 to
90d69c5
Compare
SylvainSenechal
force-pushed
the
improvement/ZENKO-5181
branch
from
34dcaad to
d0158a6
Compare
SylvainSenechal
force-pushed
the
improvement/ZENKO-5181
branch
from
d0158a6 to
1df64ba
Compare
SylvainSenechal
force-pushed
the
improvement/ZENKO-5181
branch
from
1df64ba to
11d9d19
Compare
1 participant
Issue: ZENKO-5181