-
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
create a separate crate for configuration #121
Conversation
//! Errors that can be thrown when processing configuration. | ||
|
||
/// The errors that can be thrown when processing configuration. | ||
/// | ||
/// This is effectively a copy of the `ParseError` enum in the `ndc-sdk` crate. However, we don't | ||
/// want a dependency on that crate here, as this crate is used by the CLI. Duplicating here and | ||
/// converting the values later means we can avoid that dependency. |
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.
Is the ndc-sdk
crate introducing the indirect dependency on openssl
?
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.
Yes, ndc-sdk depends on reqwest
which in turn depends on openssl
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.
LGTM!
What
Refactors the configuration code and create a new crate for it that doesn't depend on ndc-sdk directly.
Reason:
ndc-sdk
depends onreqwest
crate which callsopenssl
which in turn creates issue when creating theaarch-linux
CLI binary. There is no need forreqwest
while creating the configuration for the data connector.Doubts: I'm a little uncertain as to what errors we should be using for the configuration. I'll update the missing URI error in the PR that introduces
reading configuration URI from environment
.How