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

custom keyring data file path #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gzm55
Copy link
Contributor

@gzm55 gzm55 commented Mar 4, 2021

add an optional environment KEYRING_PROPERTY_SAGECIPHER_DATA to specify a custom keyring data file path.

close #7

@codecov
Copy link

codecov bot commented Mar 4, 2021

Codecov Report

Merging #8 (7479bbe) into master (9fcc8a9) will increase coverage by 1.18%.
The diff coverage is 80.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   46.84%   48.02%   +1.18%     
==========================================
  Files           4        4              
  Lines         269      279      +10     
==========================================
+ Hits          126      134       +8     
- Misses        143      145       +2     
Impacted Files Coverage Δ
sagecipher/keyring.py 87.09% <80.00%> (-3.38%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9fcc8a9...7479bbe. Read the comment docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

custom the data file path when used as a keyring backend
1 participant