-
Notifications
You must be signed in to change notification settings - Fork 10
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
Implement bosh integration #17
Implement bosh integration #17
Conversation
BoshCapture -> BoshQuery CloudfoundryCapture -> CloudfoundryQuery Capture -> AgentEndpoints
(Works with current implementation of pcap-api)
AgentEndpoints -> EndpointRequest
- client.go not yet used - update config.example.yml to current yaml config
- Working bosh_agent_resolver tests - mock-bosh-api reuses mock jwt and bosh api - Refactoring: EndpointQueryHandler -> AgentResolver (interface & BoshAgentResolver)
- minor optimizations to mock-bosh-api
- minor optimizations to mock-bosh-api
- use zap for logging in client - fixes for protobuf refactor/rename - integration_test: SetupBoshAgentResolver (currently non-functional (only supports one port)
- forward captureinfo fields timestamp and length from agent to client - fix logging in client
- bosh_agent_resolver.go: make setup private, include in constructor, adjust tests
- TLS configuration for pcap-bosh-cli against BoshDirectorAPI & pcap-api - refactor client - [WIP] unit tests for client - minor type change in pcap.proto - pb type fix for pcap-api-cli
(functions now public)
- move bosh-environment logic to bosh.go - clean up bosh-cli/main.go
- comments in bosh-cli/main.go - adjust tests to new Environment handling - linter fixes
BoshResolver, CfResolver
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.
First part of the review. Next is the package pcap
.
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.
next batch of files reviewed.
continuing at bosh_resolver_test.go
- integration test for client
The setup() function is called explicitly in `NewBoshResolver()`.
Add per-call location list of signals and make clear that this function is generic.
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.
Just a few things left :)
Co-authored-by: Maximilian Möhl <[email protected]>
There is a deferred exit handler already. Reuse that one but don't log the error (again) via logger if it's a flags parsing error. The flags package already prints out the error to stdout.
9013b80
to
fb03161
Compare
Also correct some error handling aronud JSON parsing.
440a797
to
3051ee7
Compare
We don't need a loop as we stop on any of the selected signals.
🎉 This PR is included in version 1.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
No description provided.