-
Notifications
You must be signed in to change notification settings - Fork 1
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 Parsec Basic Client #3
Conversation
688c665
to
e373470
Compare
40e4b1d
to
39380ed
Compare
e373470
to
1df086f
Compare
Please see results of: https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8006758451 |
c5981ce
to
6a75f7a
Compare
6a75f7a
to
1c55fc1
Compare
The order of CI execution looks a bit strange to me
this |
I think this is due to CI's way of logging, in the ci.sh script it's definitely in the right order |
f9d4083
to
57a4652
Compare
57a4652
to
987987c
Compare
987987c
to
ab0152d
Compare
Create a Parsec Provider context that contains a Parsec Basic Client. This client will be used for any operation requests coming from the Parsec Provider, so that it gets redirected to the Parsec Service. Signed-off-by: Tomás González <[email protected]>
With the new addition of the Parsec Basic Client for the Parsec Provider Context, we now need to run the Parsec Service in order to create the client and use it for testing. Signed-off-by: Tomás González <[email protected]>
Currently, errors are not displayed when they ocurr as there is no actual logger that has been included. * Add env_logger as the logging unit. * Initialize the logging unit when the provider is initialized. Signed-off-by: Tomás González <[email protected]>
ab0152d
to
d83cc22
Compare
Make the Parsec Provider context have a reference to an instance of a Parsec Basic Client. This client will be used for any operation requests coming from the Parsec Provider.