Currently the user is able to bind a single K8s secret to a YAKS test via adding labels on the secret.
The secret must hold a .properties file where all entries are automatically added as test variables.
We should enhance the support for K8s secrets so the user is able to bind multiple secrets to a test. The operator should find all secrets that are labelled with the test name and bind them to the test. Also the user should be able to specify the secret names on the test resource so the operator can bind those secrets without labels.
Also, the all secrets that contain .properties files get set as test variables automatically. Secrets with other content should be available to be loaded by the test (e.g. secrets that contain certificates and other files).
Currently the user is able to bind a single K8s secret to a YAKS test via adding labels on the secret. The secret must hold a
.propertiesfile where all entries are automatically added as test variables.We should enhance the support for K8s secrets so the user is able to bind multiple secrets to a test. The operator should find all secrets that are labelled with the test name and bind them to the test. Also the user should be able to specify the secret names on the test resource so the operator can bind those secrets without labels.
Also, the all secrets that contain
.propertiesfiles get set as test variables automatically. Secrets with other content should be available to be loaded by the test (e.g. secrets that contain certificates and other files).