-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add filters docs and external doc tests support #89
Conversation
* Add external documentation under `/docs` around filters and their configuration. * Add support for running tests in external docs. This includes adding a nightly compiler and updating cloudbuild to run them in ci. Work on #62
|
||
* Although we have in this example, a filter called `drop`, every filter in the filter chain has the same ability to *drop* or *update* a packet - if any filter drops a packet then no more work needs to be done regarding that packet so the next filter in the pipeline never has any knowledge that the dropped packet ever existed. | ||
|
||
* The filter chain is consulted for every received packet, in the same order regardless of the direction of the packet - a packet received downstream will be fed into `append` and the result from `drop` is forwarded upstream - a packet received upstream will be fed into `append` and the result from `drop` is forwarded downstream. |
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 need to instead go through the chain in reverse order when a packet goes in the opposite direction? so that e.g if we compress then encrypt, on the way back we decrypt first before decompressing.
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.
Yeah we do - this isn't implemented yet though. Would be good to have a good example (or these filters?), so we can test this is working as expected.
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.
A couple of minor things, but this is awesome 👍
I also just build the CI image and pushed it up 👍 (if you want access to be able to do that, lemme know)
cloudbuild.yaml
Outdated
@@ -23,6 +23,9 @@ steps: | |||
args: ["clippy"] | |||
id: clippy | |||
- name: gcr.io/$PROJECT_ID/ci | |||
args: ["test"] | |||
args: ["test", "--lib"] |
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.
Reading https://doc.rust-lang.org/cargo/commands/cargo-test.html and testing this out, doesn't this skip the integration tests?
Would this be better served by --tests ?
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.
Yes, good point I didn't see that caveat. Updated to use --tests instead
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.
Dooo it!
/docs
around filtersand their configuration.
adding a nightly compiler and updating cloudbuild to run them
in ci.
Work on #62