-
Notifications
You must be signed in to change notification settings - Fork 74
feat: P2P Resource manager with predefined profiles via CLI option #4629
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
base: develop
Are you sure you want to change the base?
Changes from all commits
7c1e767
3b135bd
84c4437
19c402e
4e34772
616fced
fccba40
0b66ee2
8a5481e
6a67dc0
a739fbf
975a18b
5948497
6be8b8f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -62,6 +62,7 @@ var ConfigFlags = map[string]string{ | |
| "peers": "net.peers", | ||
| "p2paddr": "net.p2paddresses", | ||
| "no-p2p": "net.p2pdisabled", | ||
| "resource-profile": "net.resourceprofile", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. UX nit: I do not see any input validation at the CLI level (i.e. --resource-profile=typo would pass al the way to buildResourceManager at startup before erroring.)
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, that's correct. In general, I can see there is limited content validation for input namely, I would be happy to add it if there is strong preference.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think what you did is fine given the state of the
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Imo, letting variables failing downstream at the package level instead of having a central validation isn't a bad direction and provides separation of concerns. However, if we were to pursue that, I would add a In addition, there are some |
||
| "allowed-origins": "api.allowed-origins", | ||
| "pubkeypath": "api.pubkeypath", | ||
| "privkeypath": "api.privkeypath", | ||
|
|
@@ -91,6 +92,7 @@ var ConfigDefaults = map[string]any{ | |
| "net.peers": []string{}, | ||
| "net.pubSubEnabled": true, | ||
| "net.relay": false, | ||
| "net.resourceprofile": "", | ||
| "keyring.backend": "file", | ||
| "keyring.disabled": false, | ||
| "keyring.namespace": "defradb", | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.