-
Notifications
You must be signed in to change notification settings - Fork 0
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
Get BiosCfg ready for prod #6
Conversation
Update config, making it uniform with other controllers Remove "store" interface Add BMC interface for later use Update rivets
db83bfc
to
6164f9d
Compare
Refactor CMD Replace old tasks and steps with new Task Replace slog with logrus. I know we want to move off logrus, but I think we need to do this at a later date. Move handler to bioscfg move publisher to bioscfg, in its own file
6164f9d
to
324f17a
Compare
Dockerfile
Outdated
FROM alpine:3.8 as runner | ||
FROM alpine:latest | ||
|
||
ENTRYPOINT ["/usr/sbin/bioscfg"] |
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.
Any reason why we moved the entrypoint
up here? I don't know that it will affect the execution, but I've never really seen it NOT be the last line of Dockerfile.
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, ill move it back. I forgot to change it back. I was dealing with a weird bug and trying some wild stuff to see what was up.
internal/store/fleetdb/client.go
Outdated
// clientID defaults to 'flipflop' | ||
clientID := "flipflop" |
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 changed to flipflop, or was this copy pasta?
internal/bioscfg/bioscfg.go
Outdated
bc := &BiosCfg{ | ||
cfg: cfg, | ||
logger: logger, | ||
ctx: ctx, |
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.
Contexts are not meant to be stored in a struct:
Do not store Contexts inside a struct type; instead, pass a Context explicitly to each function that needs it.
There's probably nothing bad that will happen if we do add it to a struct, but best to use them as intended.
What does this PR do
Attempted to put the work in their own commits to help reading, and so I dont need as many PRs.