Running integration tests against an existing environment #401
Assignees
Comments
jcrossley3
added a commit
to jcrossley3/trustification
that referenced
this issue
Aug 22, 2023
in preparation for testing against remote deployments trustification#401 Signed-off-by: Jim Crossley <jim@crossleys.org>
jcrossley3
added a commit
that referenced
this issue
Aug 22, 2023
in preparation for testing against remote deployments #401 Signed-off-by: Jim Crossley <jim@crossleys.org>
jcrossley3
added a commit
to jcrossley3/trustification
that referenced
this issue
Aug 22, 2023
Fixes trustification#401 Setting the TRUST_URL env var to a remote trustification server triggers the integs to be run against it. If it's set, other env vars will be required: TRUST_USER_ID -- the client id of the user TRUST_MANAGER_ID -- the client id of the manager TRUST_SECRET -- the secret is assumed to be the same for user & mgr If KAFKA_BOOTSTRAP_SERVERS is set, its value will be used to configure the event bus. Otherwise, SQS is assumed and valid AWS credentials will be required. Signed-off-by: Jim Crossley <jim@crossleys.org>
ctron
pushed a commit
that referenced
this issue
Aug 23, 2023
Fixes #401 Setting the TRUST_URL env var to a remote trustification server triggers the integs to be run against it. If it's set, other env vars will be required: TRUST_USER_ID -- the client id of the user TRUST_MANAGER_ID -- the client id of the manager TRUST_SECRET -- the secret is assumed to be the same for user & mgr If KAFKA_BOOTSTRAP_SERVERS is set, its value will be used to configure the event bus. Otherwise, SQS is assumed and valid AWS credentials will be required. Signed-off-by: Jim Crossley <jim@crossleys.org>
jcrossley3
added a commit
to jcrossley3/trustification
that referenced
this issue
Aug 23, 2023
ref trustification#401 & trustification#424 Signed-off-by: Jim Crossley <jim@crossleys.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment the integration tests run the trustification services as part of the test. We also need to be able to run these tests against an existing trustification instance running on a Kubernetes/OpenShift cluster.
To achieve this, the setup and spawning of trustification services must be made opt-out, and instead accept URL parameters to trustification services and credentials as required.
The text was updated successfully, but these errors were encountered: