As a first in the pydantic series, let's start with the basics. The goal of the whole series is to be able to validate the model as well as being able to generate the same json as the input, to verify we didn't miss anything.

I've working on parsing a json structure into a pydantic model. I'm planning to write a couple of posts on this. Is this something you've been playing with? Anything specific you ran into? Perhaps I could write about something specific if you have certain interests. Please let me know.

Dealing with #Ansible & #docker compose on #synology systems and an alternative #taskfile option Let's dive in: buff.ly/xoSjQ1A The alternative with taskfile: buff.ly/bMcd7SG

Using #Taskfile to deal with docker-compose vs docker compose on different systems buff.ly/bMcd7SG

Most of us already got used to annotate our #python code with typehints. If I had to guess, I would say that most people are using #mypy for checking the types. Did you know that other checkers have emerged these days?

When I encountered #uv I fell for it right away. I was already using ruff for a while and started looking into rye, which was the intermediate step before it became uv.

Previously I share a post on how you can use `uv run -s script.py` to run that script and have `uv` handle the dependencies. The original script is showing the shebang is pointing to a python3 executable.

Ever wanted to run a python script, without having to specify a virtualenv? Given buff.ly/cVEXJle we can build scripts as we would normally, though now add a few comments to it to specify the dependencies.

Poetry had a new release recently, version 2.0. Given the number, this means stuff broke ;) E.g. the poetry shell command is no more. The pyproject.toml is updated and now supporting the project header. (PEP 621) This also meant I had to update my ansible role for poetry (bartdorlandt.poetry).

I've written an article on linkedIn on my tool to migration from poetry to uv. Having uv is awesome, though the migration of each repo isn't... This tool will make your life a bit easier. Have fun 😞 https://buff.ly/3BPX5WI

Wouldn't it be great if Apple had a decent fix for the #notch on the Macs... Every time I have the Mac disconnected from the external monitor I'm annoyed by it. This time it was enough and I started looking into "fixing" it.

Another beautiful feature of #task is to include other taskfiles. Especially to have them OS specific where desired. Just include the desired #taskfile. Use `{{OS}}` to make it dynamic, allowing variables or tasks to be OS dependent. Useful for developing on Mac and running on Linux (or pipelines)

Depending on the pipeline system you're using, you might need to specify the commands to be executed yourself (jenkins, gitlab, ...) Hang on... You just created that beautiful #taskfile to make your life easier... Why not make your pipeline easier, by just executing your tasks...

Using parallelisation without thinking! That is what you can achieve with the `deps` keyword in #task. See the example on how to run your #python lint, scan and test in parallel by just running `task check`. No complications, just actions!

You are expanding your #taskfile and realise that there a couple of tasks with dependencies on a build process. Though you don't want to rebuild it, if nothing changed. #Task got you covered! Using sources and generates to monitor the source files and if the generated file exists.

Does anyone know if there is an app to have a dropdown tool for the #Mac #menubar? To have a workaround for the notch in combination with too many icons? Something like `hiddenbar`, but even better...

How to deal with #task when needing a dynamic variable or one that is stored in a file or from the output of another command... Variables can be assigned using the 'sh' key when assigned a variable. Allowing you to assign the output of any shell command. Lovely

As mentioned in my previous post, occasionally you'll need to execute a command in multiple directory or differently said, need to execute a #task multiple times. Which may involve directories, files or any action essentially. A for loop is what we need 😀

You need to run a command for some sub-directories of your project... Doing this with make, you'd need to manually put your logic in to jump back up a dir. No thinking required with #task. Just add an entry to the array, it always starts from the #taskfile location.

You have this beautiful #Taskfile helping you out. Though some systems use exec1 for a certain task, while the other use exec2. A concrete example could be 'docker-compose' vs 'docker compose'. Here is a way of working with that. ❯ task a -n task: [a] docker compose --help

The debug capability in vscode/pycharm is great! I can't imagine people debug without it. I still see too many people not using the watch feature though. It is so nice to just have a few things in focus while diving in. Here is my recommendation to check it out, if you aren't using it full time yet

Did you ever run into a #python project which you wanted to debug, but your breakpoints weren't respected... I had this the other day, having a project with pytest and pytest-cov. Apparently this messes up vscode. Mainly pytest-cov is the blocker. Try this for your launch.json.

Thoughts on Autocon2, a 🧵 Last week I attended Autocon2, put on by the Network Automation Forum networkautomation.forum/autocon2. As an extreme introvert, the non-stop interaction with various folks was absolutely exhausting, and today is the first day I feel vaguely human again. 1/?

Heard about a service called #paperless about half a year ago and I love it! Scan and store every physical mail, giving you the ability to sort and search them. What a timesaver. You could even go all out by autonumbering the documents. Running it in a docker is free.

Well, this was unexpected. Adding another api key to AWS with a different name, but the same secret_token is apparently not permitted via #terraform. resource "aws_api_gateway_api_key" "key" { name = "key" value = var.secret_token }

The Makefile has been around a long time and still being used. Though, there are alternatives out there. See this repo for a comparison and my favorite. https://github.com/bartdorlandt/Beyond_the_Makefile #make #just #bash #task #invoke

What happens when your aws lambda module is'n getting deployed... It is always in the small things. Note that `create_package = false`, isn't the same as `create = false`. Keep that in mind to save yourself some time See registry.terraform.io/modules/terr... for the different create_* options.

Something blew my mind today. In the tech community everyone has touched the jinja templating syntax at one point or another. Today I learned that the double curly braces in the template syntax are called "mustache", who knew? https://mustache.github.io/mustache.5.html :-{{

This now must be a collector item #infrahub

Good morning. Post #autocon2 coffee

Just saw this of Roger Perkin. Cisco modeling labs, 5 for free. www.rogerperkin.co.uk/cisco/get-st...

In case you were at autocon2 and didn't had enough technology this week, my interview on BMP (BGP monitoring protocol) implementation just came out. With it you can kill some time on the way back home So a bit of shameless plug 😄 packetpushers.net/podcasts/hea... I had a great time recording it.

Another day another run at #autocon2 Last day of the event. Looking forward to the talks and coffee sessions!

Had a workshop with NTC by Eric Chou and Jeff Kala. Gained a book 😁

First post on Blue Sky. Attending Autocon2, starting with a workshop on Containerlab. Looking forward to the rest as well.