-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add per-project hashing salt #371
Conversation
Avoids import errors in tests where the envvar is only set after the imports.
Also remove `test_fetch_secret` as it's not testing our actual `AzureKeyVault` class anyway
`Hasher` class sets up Azure Key vault connection and handles fetching hashing keys and project salts.
This was a bit of a pain to monkeypatch in the tests, as the call to `Hasher()` here kept trying to initiate an actual AzureKeyVault instance, which would fail because the proper environment variables are missing. Doing this at least allows us to monkeypatch the `Hasher` class in the tests so that it uses a mock keyvault instance.
… for non-existing secrets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking nice, but refactoring of keyvault won't actually cache sadly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I think some env changes are needed and a couple of questions about the public API
`environs` not used anymore, `loguru` already in core
This key was also added to the Dev Azure Keyvault
Had to create a new secret in our dev Azure Keyvault under |
Fixes #343
core.project_config.secrets.AzureKeyVault
inhasher
to set up Azure Key Vault connectionhasher
key vault functionalityhasher
knows about itTo do
main
before continuing