-
Notifications
You must be signed in to change notification settings - Fork 480
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
feat(security): Remove Writable from security services #3147
feat(security): Remove Writable from security services #3147
Conversation
LogLevel = "DEBUG" | ||
|
||
[ProxySetup] |
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.
Why was this added?
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.
no particular strong reason, i just felt that it can be more structural in this way since potentially you can have many more RequestTimout
for that naming alone.
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.
It is redundant since this is Proxy Setup's
specific configuration. IMO, the extra level isn't needed. We added the extra levels in the bootstrapper config to make the Env override more readable, but that isn't needed here.
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.
fixed.
15c04cc
to
377e5e1
Compare
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
Update for security services on: - Loglevel is on the top level of ConfigurationStruct - Remove Writable from Configuration struct - Make UpdateFromRaw, UpdateWritableFromRaw do nothing and make EmptyWritablePtr just return nil Fixes: edgexfoundry#3123 Signed-off-by: Jim Wang <yutsung.jim.wang@intel.com>
1328e27
to
266ed88
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Update for security services on:
Fixes: #3123
Signed-off-by: Jim Wang yutsung.jim.wang@intel.com
PR Checklist
Please check if your PR fulfills the following requirements:
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?
security services have Writable struct but actually it never uses
Issue Number: #3123
What is the new behavior?
Refactor the
LogLevel
inside Writable struct and remove Writable.Does this PR introduce a breaking change?
New Imports
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Depends on PR #2863 as the redis' toml conf would also be removed about the Writable section.
Other information