-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-12998] [Playground] Environment service #15654
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
Conversation
playground/backend/internal/environment/environment_service_test.go
Outdated
Show resolved
Hide resolved
| import "io" | ||
|
|
||
| // LogWriters contains writes for logger. Writers should implement io.Writer interface. | ||
| type LogWriters struct { |
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.
May we consider having a separate internal/log package? I like that we are centralizing logging and I would additionally propose enforcing structured logging. I've seen two approaches. One, using the uber zap library. Another using the native go library but logging out a struct adherent to https://pkg.go.dev/google.golang.org/cloud/logging#Entry. In the second case, just the Entry is populated and written out to stdout or stderr without using logging.Client. In GCP, structured logs are automatically parsed with the applied key/value pairs. I've used both approaches and found the second more flexible as there are settings where one just wants a single line string in the log.
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.
We've removed logs from this package and consider to implement them in a separate package in the new pr, will submit them soon :)
cfb6ed4 to
465a5d5
Compare
|
What is the next step on this PR? |
e8f495d to
2a3f274
Compare
|
@damondouglas - it seems like @ilya-kozyrev addressed your comments. Is that correct? |
2a3f274 to
0802804
Compare
damondouglas
left a comment
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.
@pabloem LGTM
… cache and application envs Co-authored-by: AydarZaynutdinov <aydar.zaynutdinov@akvelon.com> Co-authored-by: daria.malkova <daria.malkova@akvelon.com>
980ffb3 to
aa26b53
Compare
|
@pabloem rebased on master. Could you please merge it? |
LogWriters contains writes for the logger. Writers should implement io.Writer interface.logging will be implemented in next PRsThank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunnercompliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.