Docker based version of Conjur CLI allows configuration using environment variables the same way a summon-conjur does (see https://github.com/cyberark/summon-conjur#configuration). This is not possible with this implementation.
Steps to Reproduce
Steps to reproduce the behavior:
export CONJUR_ACCOUNT, CONJUR_APPLIANCE_URL, CONJUR_SSL_CERTIFICATE, CONJUR_AUTHN_LOGIN and CONJUR_AUTHN_API_KEY environment variables
run conjur list
It will ask you to initialize Conjur CLI even though you provided all the information
Expected Results
Run conjur command without any file configuration
Actual Results (including error logs, if applicable)
Requires you to run the conjur init first
Reproducible
[x] Always
[ ] Sometimes
[ ] Non-Reproducible
Version/Tag number
Works as expected in docker version cyberark/conjur-cli:5, does not work in the latest version of the Python implementation of Conjur CLI (v7.0.1)
Additional Information
I supposed this implementation should have kept the core functionality of the docker one that is why I am reporting it as a bug.
Summary
Docker based version of Conjur CLI allows configuration using environment variables the same way a summon-conjur does (see https://github.com/cyberark/summon-conjur#configuration). This is not possible with this implementation.
Steps to Reproduce
Steps to reproduce the behavior:
conjur list
Expected Results
Run
conjur
command without any file configurationActual Results (including error logs, if applicable)
Requires you to run the
conjur init
firstReproducible
Version/Tag number
Works as expected in docker version cyberark/conjur-cli:5, does not work in the latest version of the Python implementation of Conjur CLI (v7.0.1)
Additional Information
I supposed this implementation should have kept the core functionality of the docker one that is why I am reporting it as a bug.