Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
imheresamir opened this issue Jun 1, 2021 · 1 comment

Comments

@imheresamir
Copy link
Contributor

imheresamir commented Jun 1, 2021

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 #307 (comment)

@imheresamir imheresamir changed the title E2E workflow scripts should infer which flavor of Conjur has been deployed to the cluster E2E Workflow Scripts: Infer which flavor of Conjur has been deployed to the cluster Jun 1, 2021
@imheresamir imheresamir changed the title E2E Workflow Scripts: Infer which flavor of Conjur has been deployed to the cluster E2E Workflow Scripts: Workflow should be agnostic to which flavor of Conjur has been deployed to the cluster Jun 3, 2021
@jtuttle jtuttle closed this as completed Aug 2, 2021
@jtuttle jtuttle reopened this Aug 2, 2021
@jtuttle
Copy link
Member

jtuttle commented Aug 2, 2021

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.

@jtuttle jtuttle changed the title E2E Workflow Scripts: Workflow should be agnostic to which flavor of Conjur has been deployed to the cluster E2E Workflow Scripts: Workflow should infer which flavor of Conjur has been deployed to the cluster Aug 2, 2021
@jtuttle jtuttle changed the title E2E Workflow Scripts: Workflow should infer which flavor of Conjur has been deployed to the cluster E2E Workflow Scripts: Workflow should detect which flavor of Conjur has been deployed to the cluster Aug 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants