Repository navigation
azure key vault sync, changed-only bitwarden - #31
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
adds
hush sync azurekv --vault NAME [--dry-run] [--exclude NAME] [names], and makes bitwarden skip an item whose password already matches.azure uses the az login you already have. the cli hands over a short-lived token and a small node helper compares and PUTs each value over https, so neither the token nor a value lands on argv, in output or in a file. it compares against the vault's current value, so there is no cursor to drift and a remote edit gets repaired on the next run. a local delete never deletes remotely. names must already be azure-safe (lowercase, digits, hyphens), no lossy mapping.
whole-file targets are unchanged. no new scheduler, credential or vault permission. version stays 1.7.0 until a release.
tests use fake providers: azure 18, bitwarden 20, lastpass 27, keepass 18, bitwarden schedule 7. the two new bitwarden unchanged-value checks fail on 1.7.0, and dropping the azure equality check fails the repeat-run no-PUT test.
not proven yet: a live azure vault (auth, permissions, transport) and native linux and windows runs.
refs #30