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

Add Parsec Basic Client #3

Merged
merged 3 commits into from
Mar 6, 2024
Merged

Add Parsec Basic Client #3

merged 3 commits into from
Mar 6, 2024

Conversation

tgonzalezorlandoarm
Copy link
Member

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.

@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm
Copy link
Member Author

@gowthamsk-arm
Copy link
Collaborator

The order of CI execution looks a bit strange to me

+ openssl version
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
+ pushd /tmp/parsec
/tmp/parsec /tmp/parsec-openssl-provider
+ popd
/tmp/parsec-openssl-provider
+ wait_for_service
++ pgrep parsec
+ ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml
+ '[' -z 8 ']'
+ sleep 5
+ pgrep parsec

this ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml runs after wait_for_service??

@tgonzalezorlandoarm
Copy link
Member Author

The order of CI execution looks a bit strange to me

+ openssl version
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
+ pushd /tmp/parsec
/tmp/parsec /tmp/parsec-openssl-provider
+ popd
/tmp/parsec-openssl-provider
+ wait_for_service
++ pgrep parsec
+ ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml
+ '[' -z 8 ']'
+ sleep 5
+ pgrep parsec

this ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml runs after wait_for_service??

I think this is due to CI's way of logging, in the ci.sh script it's definitely in the right order

@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm
Copy link
Member Author

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]>
@gowthamsk-arm gowthamsk-arm merged commit 83c2ecd into main Mar 6, 2024
7 checks passed
@tgonzalezorlandoarm tgonzalezorlandoarm deleted the tg/keymanagement branch March 28, 2024 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants