Another silly thing that isn't

The cookie jar is ready to uh... rumble?

That little `pipeline-renderer` fence is an isomorphic view of the same tool that I use to tick the graph, the glowing Ruby heart at the core of the thing.

It exists as:

`jeeves render template` :: the cli jenkins activated beating heart
`apirah /pipleine/render` :: the rack based solution to cold starts
`wooster pipeline render` :: the go based API client based solution to needing CLI based heartbeats
`pipeline-renderer` :: some thing i just asked for on a whim

The intent to reality time for each of those is decreasing at an exponential rate

Today it took about 30s and they misheard me anyways (but had figured it out, it helps to stay thematically coherent in your tooling universes)

#devops #devopsendgamewithallthecheatcodes #devopsoneasymode #engineering #cbpsok

She does tend to go on a bit doesn't she...

[no one ask where she gets that from]

This is the post-amble, mainly release coordination, direct Cloudflare updates for integration builds, preprod and production_staging are integrated back into a larger orchestrator.

Components are what we're producing, the output of our function.

In this case, bog standard ECS. I'll spare you the gory details, the rest of it is a few more pages of ENV vars and what you would recognize as the API definitions for CreateService^UpdateService and RegisterTask with a lot of purple beside them

Below that come the environments. These another component in the multi-dimensional vector that is the input to the Peregrine function

Peregrine(artifact^environment) makes the full function

And these are mostly secrets so that's as far as we go

!Environment and !Mapped are the same aside from !Environment = !Mapped [external context].[path]

I've had an idea for that external context

#devops #engineering #devopsoneasymode

And now for the 2nd order tools.

Tools that consume the APIs that the textual computers embedded in the node graphs expose.

[It's a todo list isn't it... it's always a todo list]

It's `toodles` my CLI todo list manager

[It's a demonstration of click based CLI wrappers for APIs exposed by fences (functions) and virtual-fences (textual computational fever dreams of a hyperlexic mind) as a pattern for my team to start to follow to build their own tools]

It's called `toodles` y'all

Toodles

F : Todo(1) -> Todo(2) is the identity

Honk(X,toodles) ~= Honk(X,:::wanderland-todo-list) for all known X

#engineering #devops #devopsoneasymode #devopsendgamewithallthecheatcodes

It must be that time of day where we start winding up

🎁 ⏰

Look what I found, a new oculus CLI for calling fences. Joins neovim, and MCP as clients of the API (sorry #emacs, you're coming).

And so I did the needful...

Touche 🔮 touche

Fences are first class functions in #wanderland

And now there's a first class CLI to go with it

How many of you build tools for a living?

How many of you can do it by just writing a markdown file? That's also the manual? And the tests? And the storage? And the API?

It's wonderful in #wanderland, weirdly wonderful

#devops #devopsendgamewithallthecheatcodes #devopsoneasymode #engineering

It does take a bit of the fun away doesn't it

[who am I kidding of course it doesn't... the fun was never in slogging over code was it? ... was it?]

#devopsoneasymode #wanderland #waitthatworked #wonderfullyweird #engineering