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

Auto PR: feature/mq-crypto #301

Closed
wants to merge 1 commit into from
Closed

Auto PR: feature/mq-crypto #301

wants to merge 1 commit into from

Conversation

stackibot
Copy link

No description provided.

@masonkatz masonkatz force-pushed the feature/mq-crypto branch 3 times, most recently from 4b522ed to a4472fa Compare October 8, 2018 23:31
@masonkatz masonkatz force-pushed the feature/mq-crypto branch 3 times, most recently from 1c6962f to df986a9 Compare October 26, 2018 21:26
@masonkatz masonkatz force-pushed the feature/mq-crypto branch 2 times, most recently from f5c5fd1 to b61c151 Compare November 13, 2018 00:25
@masonkatz masonkatz force-pushed the feature/mq-crypto branch 3 times, most recently from f1ab77b to c7ead2b Compare November 26, 2018 22:06
Split the shadow attributes out of the `cluster` database and into a
their own `shadow` database. This is the start of a locked down secrets
database where host keys and other things can be stored.

BREAKING CHANGE:

Added a whole new database and redid permissions. This is a scorched earth
commit, with no path forward for existing Frontends.

INTERNAL: Added `--bootstrap` flag to pip2src
@masonkatz masonkatz closed this Dec 10, 2018
@masonkatz masonkatz deleted the feature/mq-crypto branch December 10, 2018 21:06
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.

2 participants