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

Added provider names to the config. #491

Conversation

MattDavis00
Copy link
Member

This is an optional field and defaults to a suitable name for each provider if it is not provided.

Two providers cannot have the same name.

Closes #487

Signed-off-by: Matt Davis [email protected]

@MattDavis00 MattDavis00 requested a review from a team as a code owner July 27, 2021 11:43
@MattDavis00 MattDavis00 changed the base branch from main to feature-sqlite-kim July 28, 2021 11:23
Copy link
Member

@ionut-arm ionut-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a couple of small comments

config.toml Show resolved Hide resolved
src/utils/config.rs Outdated Show resolved Hide resolved
config.toml Show resolved Hide resolved
@MattDavis00 MattDavis00 force-pushed the feature-provider-names branch 5 times, most recently from de3c267 to 38e1f20 Compare July 29, 2021 12:53
Copy link
Member

@ionut-arm ionut-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall, just one minor comment

src/providers/cryptoauthlib/mod.rs Outdated Show resolved Hide resolved
Copy link
Member

@hug-dev hug-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since you are doing all the work on a separate feature branch, this is totally fine to merge things little by little. I think it would be nice to have in a future PR some config tests:

  • checking that the service starts with multiple providers of the same type with different names
  • checking that the service fails to start with multiple providers of the same type with the default name
  • creating a key with a provider of type A then restarting the service with a configuration where a new provider of the type A is added but check that the key can still be accessed

src/back/backend_handler.rs Outdated Show resolved Hide resolved
src/utils/service_builder.rs Outdated Show resolved Hide resolved
src/utils/service_builder.rs Outdated Show resolved Hide resolved
src/utils/service_builder.rs Show resolved Hide resolved
This is an optional field, and will default to a suitable name for each provider if it is not provided.

Two providers cannot have the same name.

Closes parallaxsecond#487

Signed-off-by: Matt Davis <[email protected]>
Copy link
Member

@hug-dev hug-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes! We can always change things here in the future as this feature develops

Copy link
Member

@ionut-arm ionut-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

@MattDavis00 MattDavis00 merged commit 6f7ec9f into parallaxsecond:feature-sqlite-kim Jul 30, 2021
@MattDavis00 MattDavis00 deleted the feature-provider-names branch September 2, 2021 14:47
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.

Add Provider Name Config Option
3 participants