Category: PipeLayer
A new event step_end was added in v0.7.0. It passes the manifest_entry and data in the event args. This example shows how the step_end event could be used to log the manifest_entry for each step in a pipeline:
First things first: It’s been a little over a month since the first version of PipeLayer was published and to celebrate, it got a shiny new logo! Events that were added to the Filter abstract class have been extended to the Pipeline and Switch by inheriting from the Filter abstract class. With the addition of […]
This release introduces Filter Events, and Pipeline Actions. These events are raised by the Filter object: start exit end They can be handled by attaching a callable to each event. The start and end events are raised automatically, but the exit event is triggered by setting the action in the event handler to either EXIT, […]
It’s that time. Another week, another new version. This one has only one visible addition: The Switch filter. It works (and reads) very much like it’s counterparts in C# and JavaScript: Under the hood, I needed to make the step init functions public. I moved them out of the Pipeline and into a new StepHelper […]
The is only one notable change in 0.3.1: The pipelayer.Step base class was converted to an interface (a Protocol). This means for your implementation, all you need to do is create a class that implements a run method with this signature: As I continued to work on the microservice example (using v0.3.0), I found I […]
As soon as I’d published the last version to PyPi, I’d started on the next round of improvements. Both the Pipeline and Filter class had a run method (diff signatures though), so how hard would it be to nest a Pipeline to be added alongside the filters? It turns out, not nearly has difficult as […]
As I was creating some “real-world” scenarios to test, I realized that requiring filters to derive from the Filter class was not necessary. As long as the method signature for a static/module/lambda was the same, any function could easily be added to a pipeline. Stay tuned, version 0.3.0 was passing tests within an hour of […]
After two years of working on a few microservices projects (mostly Python-based), with varying architectures and program flow, and after lengthy brainstorming discussions with one of the client engineers on my current project, I started to come up with a rough idea of a generic, reusable framework. Within a week after writing the first line […]