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

cryptography: Enable ability for a standalone build #27

Closed

Conversation

bramoosterhuis
Copy link
Contributor

This is to break a cyclic build dependency between clientlibraries and libprovision, if we move to a vault implementation of libprovision. In existing builds, it will still build as part of clientlibraries. This just gives the option to invoke a build directly in Source/cryptography without moving cryptography in a separate repo.

Current cyclic dependency if we move to the vault powered libprovision:

  • libproviosion -> clientlibraries(cryptography)
  • clientlibraries(provisionproxy) -> libproviosion

@pwielders
Copy link
Contributor

I think we can close this? @bramoosterhuis

@pwielders pwielders closed this Mar 2, 2021
@pwielders pwielders deleted the development/crytography-standalone-build branch March 2, 2021 08:28
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