search

cyberark / conjur-authn-k8s-client

Authentication sidecar for Conjur Kubernetes integration.
https://www.conjur.org
Apache License 2.0
11 stars 14 forks source link

E2E Workflow Scripts: Workflow should detect which flavor of Conjur has been deployed to the cluster #317

Open imheresamir opened 3 years ago

imheresamir commented 3 years ago

Describe the solution you would like

E2E workflow scripts should be agnostic to which flavor of Conjur (Enterprise or OSS) has been deployed to the cluster rather than setting this with the CONJUR_OSS_HELM_INSTALLED environment variable.

  1. Deploy Conjur (in whatever flavour)
  2. Extract any details from deployed Conjur that might be needed for later
  3. The example below shows a snippet of code that could be substituted with a value explicitly retrieved from (2) 
    if [[ "$CONJUR_OSS_HELM_INSTALLED" == "true" ]]; then
conjur_service='conjur-oss'
else
conjur_service='conjur-master'
fi
conjur_url=${CONJUR_APPLIANCE_URL:-https://$conjur_service.$CONJUR_NAMESPACE.svc.cluster.local}

_Originally posted by @doodlesbykumbi in https://github.com/cyberark/conjur-authn-k8s-client/pull/307#discussion_r635975648_

jtuttle commented 3 years ago

The intent of this story is to have the test scripts be able to automatically detect which version of Conjur they're talking to, possibly by querying the /info endpoint. This is squarely in the "nice-to-have" category for the time being. It will likely require some spiking and design before we can point it.