#yaml — Public Fediverse posts

Heute mal wieder drei Stunden damit verbracht, ein Problem zu debuggen, das sich am Ende als fehlendes Komma in der Config rausgestellt hat. Der YAML-Parser hat natürlich nur "unexpected token" gemeckert, weil ausführliche Fehlermeldungen offenbar gegen die Genfer Konvention verstoßen.

Kaffee Nummer vier ist unterwegs. ☕

#YAML #DevLife #OpenSource

We just released vscode-yaml and yaml-language-server 1.23.0! It reverted the formatter changes we made in 1.22.0, since they caused regressions. View the full changelog here: https://github.com/redhat-developer/vscode-yaml/releases/tag/1.23.0

#vscode #yaml

💡 Quick! Call the #innovation police! We've got a #rogue #developer "overcoming #AI psychosis" by scribbling specs in #YAML ✍️ while dreaming of #markdown 🙄. Meanwhile, their DIY #toolkit promises to revolutionize... absolutely nothing. 🚀🔍
https://acai.sh/blog/specsmaxxing #police #psychosis #HackerNews #ngated

Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML

https://acai.sh/blog/specsmaxxing

#HackerNews #Specsmaxxing #AI #Psychosis #YAML #Writing

Oh joy, another "dashboard as code" tool with a dash of #YAML and a sprinkle of JSX! 🤖✨ Now, even your AI agents can join in the tedium of creating "standardized" dashboards, because who needs creativity when you have a "builtin semantic layer," am I right? 🙄👨‍💻 Just what the internet needed, more ways to make boring data look marginally less boring. 🍵💻
https://github.com/bruin-data/dac #dashboardascode #JSX #AIAgents #datavisualization #HackerNews #ngated

🤔 Oh, brilliant! More layers to manage—because #Kubernetes wasn't convoluted enough already. 🎢 Dive into this riveting tale of a container managing containers on a shipwreck of other containers. It’s like #Inception, but with more #YAML and fewer plot twists. 📉
https://github.com/rancher/k3k #ContainerManagement #DevOps #HackerNews #ngated

I built something nice for my solar panels and solix in #homeassistant. It´s a dynamic max for grid import. #yaml

The next #LightningTalk at #OggCamp was about Self-hosted Observability, using various #Grafana projects and #Prometheus etc.
Alan was using some #YAML files to provision the services via docker etc.

I didn't quite understand it all, but there's a few extra Grafana products I should check out - Alloy and Mimir.

https://github.com/alanionita/observability-stack

#selfhosting #metrics

От каши к структуре: гибридная AI-система для обработки свободного текста

Как превратить десятки неструктурированных описаний участников сообщества в систему поиска Занимаюсь бэкендом лет 7, Go и Python, немного ML» — попробуйте найти среди двухсот таких описаний нужного человека. Руками — часы. Я автоматизировал это через гибрид LLM + детерминированного кода, и отловил все возможные проблемы. Рассказываю про архитектуру, промпты и решения. * На обложке — Архимболдо «Библиотекарь» (1566): из разрозненных книг складывается цельный образ. Как и профиль участника в системе

https://habr.com/ru/articles/1027724/

#LLM #структурирование_данных #гибридная_архитектура #нормализация #Python #Qwen #YAML #поиск_по_профилям #нетворкинг #обработка_естественного_языка

#yaml is a lousily tiped #language

En parlant de réécriture, je procrastine toujours celle de la configuration de @DNS_Shaftinc en #Yaml.

Pas de caractère contraignant pour le moment mais qui sait ce que nous réserve le futur 🤔

Pavel just released new version of vcs-diff-lint 🛠️ The tool (+ GitHub action) for differential code linting.

The highlight: Newly with yamllint support!

Bonus: Fedora's Forgejo instance integration experiment (infra ansible repo):
https://forge.fedoraproject.org/infra/ansible/pulls/3304

#Ansible #YAML #Linter #CI #GitHubAction #FedoraInfra

Единое окно инженера данных: как мы построили веб-среду разработки для 12 000 потоков данных

Привет, Хабр! Меня зовут Никита Калганов, я ведущий системный инженер данных в X5 Tech. Мы с командой проектируем и развиваем высоконагруженную систему потоков данных и поддерживаем её в условиях постоянного роста, как по числу потоков, так и по количеству команд, которые с ней работают. В нашей системе обработки данных живёт больше двенадцати тысяч потоков данных, и их число растёт в среднем на несколько десятков в день. Всё нормально работает, но мы решили сделать её ещё лучше. В этой статье расскажу, как мы построили единое окно инженера данных, сделали собственный DDL-мигратор с поддержкой зависимостей и при этом сохранили то, что уже работает.

https://habr.com/ru/companies/X5Tech/articles/1026382/

#большие_данные #big_data #lakehouseплатформа_данных #data_pipelines #airflow #yaml #gitlab_cicd #микросервисная_архитектура #оркестрация #ddl

Единое окно инженера данных: как мы построили веб-среду разработки для 12 000 потоков данных

Привет, Хабр! Меня зовут Никита Калганов, я ведущий системный инженер данных в X5 Tech. Мы с командой проектируем и развиваем высоконагруженную систему потоков данных и поддерживаем её в условиях постоянного роста, как по числу потоков, так и по количеству команд, которые с ней работают. В нашей системе обработки данных живёт больше двенадцати тысяч потоков данных, и их число растёт в среднем на несколько десятков в день. Всё нормально работает, но мы решили сделать её ещё лучше. В этой статье расскажу, как мы построили единое окно инженера данных, сделали собственный DDL-мигратор с поддержкой зависимостей и при этом сохранили то, что уже работает.

https://habr.com/ru/companies/X5Tech/articles/1026382/

#большие_данные #big_data #lakehouseплатформа_данных #data_pipelines #airflow #yaml #gitlab_cicd #микросервисная_архитектура #оркестрация #ddl

Единое окно инженера данных: как мы построили веб-среду разработки для 12 000 потоков данных

Привет, Хабр! Меня зовут Никита Калганов, я ведущий системный инженер данных в X5 Tech. Мы с командой проектируем и развиваем высоконагруженную систему потоков данных и поддерживаем её в условиях постоянного роста, как по числу потоков, так и по количеству команд, которые с ней работают. В нашей системе обработки данных живёт больше двенадцати тысяч потоков данных, и их число растёт в среднем на несколько десятков в день. Всё нормально работает, но мы решили сделать её ещё лучше. В этой статье расскажу, как мы построили единое окно инженера данных, сделали собственный DDL-мигратор с поддержкой зависимостей и при этом сохранили то, что уже работает.

https://habr.com/ru/companies/X5Tech/articles/1026382/

#большие_данные #big_data #lakehouseплатформа_данных #data_pipelines #airflow #yaml #gitlab_cicd #микросервисная_архитектура #оркестрация #ddl

Единое окно инженера данных: как мы построили веб-среду разработки для 12 000 потоков данных

Привет, Хабр! Меня зовут Никита Калганов, я ведущий системный инженер данных в X5 Tech. Мы с командой проектируем и развиваем высоконагруженную систему потоков данных и поддерживаем её в условиях постоянного роста, как по числу потоков, так и по количеству команд, которые с ней работают. В нашей системе обработки данных живёт больше двенадцати тысяч потоков данных, и их число растёт в среднем на несколько десятков в день. Всё нормально работает, но мы решили сделать её ещё лучше. В этой статье расскажу, как мы построили единое окно инженера данных, сделали собственный DDL-мигратор с поддержкой зависимостей и при этом сохранили то, что уже работает.

https://habr.com/ru/companies/X5Tech/articles/1026382/

#большие_данные #big_data #lakehouseплатформа_данных #data_pipelines #airflow #yaml #gitlab_cicd #микросервисная_архитектура #оркестрация #ddl

In the workshop today we called #YAML a "weapon of mass description".
And we agreed it should be subject to the Geneva convention as it induces eye cancer 🥴

We just released VS Code YAML 1.22.0. Notable improvements include dropping prettier as a dependency, being able to use `# $schema: <url>` to specify a schema, and improved Kubernetes support out of the box. See the full CHANGELOG here: https://github.com/redhat-developer/vscode-yaml/blob/main/CHANGELOG.md#1220
#yaml #vscode #kubernetes

I love #yaml. It’s so great /s

𝗞𝗲𝘆𝘀𝘁𝗮𝘁𝗶𝗰:

#ContentManagment #Markdown #JSON #YAML #Keystatic

https://thewhale.cc/posts/keystatic

Content Management for your Codebase. A tool that makes Markdown, JSON and YAML content in your codebase editable by humans. Live edit content on GitHub or your local file system, without disrupting your existing code and workflows.

Как мы извлекали модель подразделения из живой конфигурации и находили расхождения с регламентом

Когда в компании говорят о модели подразделения, обычно имеют в виду что-то вполне привычное: положение об отделе, регламент, SLA, список ролей и зон ответственности. Формально этого достаточно: подразделение описано, обязанности зафиксированы, сроки обозначены. Но как только возникает практический вопрос — а как это подразделение на самом деле работает изо дня в день, по каким правилам движутся задачи, где реально проверяются сроки, какие данные обязательны на входе и что система делает без участия человека, — быстро выясняется, что документов недостаточно. Если в компании внедрено ПО для автоматизации, значимая часть настоящей модели подразделения живёт в конфигурации системы: в состояниях, переходах, правах, обязательных полях, автоматизациях, событиях и скрытых технических правилах. Если смотреть только в документы, получится аккуратная управленческая картина. Если смотреть только в конфигурацию, можно увидеть механику, но потерять смысл. Реальное устройство подразделения возникает только на пересечении этих двух слоёв. В ежедневной рабочей рутине это не проявляется, но если у отдела меняется руководитель, процессы нужно масштабировать на новый филиал или к работе подключается подрядчик, разрыв становится проблемой, и решить её быстро не всегда получается. Меня зовут Денис Селезнёв, я генеральный директор компании «Первая Форма». Мы занимаемся автоматизацией бизнес-процессов уже более 20 лет. В последнее время мы активно развиваем новый подход к оцифровке бизнесов — Организация как код, о нём я рассказывал вот в этой статье. В рамках OaC мы решили взять живую конфигурацию, извлечь из неё формальную модель подразделения и сравнить её с тем, что написано в регламенте. Эта статья — о том, что получилось.

https://habr.com/ru/companies/1forma/articles/1023170/

#bpms #yaml #автоматизация #автоматизация_процессов #корпоративные_системы #lowcode #первая_форма #aiагенты #ai #корпоративные_процессы

It turns out there are no YAML-specific editors. There really needs to be.

Yes, I know it’s just a text file and most code editors understand YAML I just want a YAML editor, that understands structured YAML.

#yaml #editor #programming

Ein falsches Leerzeichen in #YAML & das Deployment schlägt fehl. @wlami zeigt, wie Infrastructure as Code auch anders funktioniert: typsicher, testbar & direkt in #Java!

Neugierig, wie das in der Praxis aussieht?
Lese: https://javapro.io/de/schluss-mit-yaml-cloud-infrastruktur-in-purem-java-definieren-testen-und-deployen/

#DevOps #Cloud #JAVAPRO @PulumiCorp

One thing I think people aren't talking enough about is how #genAI has made #Markdown as ubiquitous a document format as #XML was in the early '00s.

Of course the great thing for us programmers is that it is almost as poorly specified and ambiguous as #YAML.

We are so good at this standards stuff.

RE: https://w3c.social/@w3c/116216070362563670

FWIW, I have been storing Linked Data (including ActivityPub) in an INI like format — because I find INI-like formats more human-friendly (to both read and write) than JSON.

YAML is probably better than JSON, too, in that respects. But I think INI-like formats are better than YAML.

#ActivityPub #ActivityStreams #JSONLD #LinkedData #RDF #YAML #YAMLLD

New project: mosscap. I needed a small tool to automate certain shell tasks with a simple easy to use configuration system. I didn't find one that suited me, so I made my own.

Miss so turns out to be pretty, powerful and flexible. You can parallelize tasks, have comprehensive logging, interactive abort between actions etc.

Try it out: https://codeberg.org/scip/mosscap

#golang #cli #automate #commandline #linux #yaml

#pyinfra - Du #Python au lieu du #YAML d' #Ansible pour gérer vos #serveurs

Jusqu'à 10x plus rapide qu' #Ansible sur déploiements massifs

https://korben.info/pyinfra-automatisation-infrastructure-python.html

Why is #JavaScript so popular? I hate everything about it.

I'm speaking at the #Canberra Field #Naturalists meeting at #ANU next month on #Malaise trapping and the #insects and other #invertebrates that surround us without our noticing them.

I expect most of my slides to be arrays of four or six #microscope images with a header (probably a family name in most cases) and captions for each image.

I don't want to lay out all these images in #LibreOffice (or any similar presentation tool) because I'm a perfectionist and getting it all tidy will take forever.

So, I decided to try out #Slidev, #Marp and other #Markdown-based presentation tools. The Markdown part is very appealing, but they all lean hard into JavaScript. That would be fine so long as I don't have to think about that side of things.

Slidev's AppleBasic theme seemed to be the best starting point, so I started hacking it to add som extra gridded image views. Plain image grids were not too challenging, but I really want captions for each image, so I started trying to understand how the templates use the forest of underlying JS libraries and CSS artefacts to produce the displayed slides.

Frankly, the whole thing is so opaque and would take me much longer to understand than preparing multiple presentations by hand would.

Then I realised I can use #montage on the command line to produce the kind of layouts I want, and I can script #exiftool to extract and prepare the captions which will save time.

So, my new plan is to write a #Python script that processes a #YAML file listing all the slides, titles and image paths. It can generate PNG images that are close to the target 1920*1080 size (give or take a little). I'll then use LibreOffice for a couple of more text-oriented or irregular slides, export those and combine all the images into a PDF.

I'm sure this will be way faster than battling Node.js. Not sure why I felt I had to write it up.

https://fieldnatsact.com/

Why is #JavaScript so popular? I hate everything about it.

I'm speaking at the #Canberra Field #Naturalists meeting at #ANU next month on #Malaise trapping and the #insects and other #invertebrates that surround us without our noticing them.

I expect most of my slides to be arrays of four or six #microscope images with a header (probably a family name in most cases) and captions for each image.

I don't want to lay out all these images in #LibreOffice (or any similar presentation tool) because I'm a perfectionist and getting it all tidy will take forever.

So, I decided to try out #Slidev, #Marp and other #Markdown-based presentation tools. The Markdown part is very appealing, but they all lean hard into JavaScript. That would be fine so long as I don't have to think about that side of things.

Slidev's AppleBasic theme seemed to be the best starting point, so I started hacking it to add som extra gridded image views. Plain image grids were not too challenging, but I really want captions for each image, so I started trying to understand how the templates use the forest of underlying JS libraries and CSS artefacts to produce the displayed slides.

Frankly, the whole thing is so opaque and would take me much longer to understand than preparing multiple presentations by hand would.

Then I realised I can use #montage on the command line to produce the kind of layouts I want, and I can script #exiftool to extract and prepare the captions which will save time.

So, my new plan is to write a #Python script that processes a #YAML file listing all the slides, titles and image paths. It can generate PNG images that are close to the target 1920*1080 size (give or take a little). I'll then use LibreOffice for a couple of more text-oriented or irregular slides, export those and combine all the images into a PDF.

I'm sure this will be way faster than battling Node.js. Not sure why I felt I had to write it up.

https://fieldnatsact.com/

Why is #JavaScript so popular? I hate everything about it.

I'm speaking at the #Canberra Field #Naturalists meeting at #ANU next month on #Malaise trapping and the #insects and other #invertebrates that surround us without our noticing them.

I expect most of my slides to be arrays of four or six #microscope images with a header (probably a family name in most cases) and captions for each image.

I don't want to lay out all these images in #LibreOffice (or any similar presentation tool) because I'm a perfectionist and getting it all tidy will take forever.

So, I decided to try out #Slidev, #Marp and other #Markdown-based presentation tools. The Markdown part is very appealing, but they all lean hard into JavaScript. That would be fine so long as I don't have to think about that side of things.

Slidev's AppleBasic theme seemed to be the best starting point, so I started hacking it to add som extra gridded image views. Plain image grids were not too challenging, but I really want captions for each image, so I started trying to understand how the templates use the forest of underlying JS libraries and CSS artefacts to produce the displayed slides.

Frankly, the whole thing is so opaque and would take me much longer to understand than preparing multiple presentations by hand would.

Then I realised I can use #montage on the command line to produce the kind of layouts I want, and I can script #exiftool to extract and prepare the captions which will save time.

So, my new plan is to write a #Python script that processes a #YAML file listing all the slides, titles and image paths. It can generate PNG images that are close to the target 1920*1080 size (give or take a little). I'll then use LibreOffice for a couple of more text-oriented or irregular slides, export those and combine all the images into a PDF.

I'm sure this will be way faster than battling Node.js. Not sure why I felt I had to write it up.

https://fieldnatsact.com/

Why is #JavaScript so popular? I hate everything about it.

I'm speaking at the #Canberra Field #Naturalists meeting at #ANU next month on #Malaise trapping and the #insects and other #invertebrates that surround us without our noticing them.

I expect most of my slides to be arrays of four or six #microscope images with a header (probably a family name in most cases) and captions for each image.

I don't want to lay out all these images in #LibreOffice (or any similar presentation tool) because I'm a perfectionist and getting it all tidy will take forever.

So, I decided to try out #Slidev, #Marp and other #Markdown-based presentation tools. The Markdown part is very appealing, but they all lean hard into JavaScript. That would be fine so long as I don't have to think about that side of things.

Slidev's AppleBasic theme seemed to be the best starting point, so I started hacking it to add som extra gridded image views. Plain image grids were not too challenging, but I really want captions for each image, so I started trying to understand how the templates use the forest of underlying JS libraries and CSS artefacts to produce the displayed slides.

Frankly, the whole thing is so opaque and would take me much longer to understand than preparing multiple presentations by hand would.

Then I realised I can use #montage on the command line to produce the kind of layouts I want, and I can script #exiftool to extract and prepare the captions which will save time.

So, my new plan is to write a #Python script that processes a #YAML file listing all the slides, titles and image paths. It can generate PNG images that are close to the target 1920*1080 size (give or take a little). I'll then use LibreOffice for a couple of more text-oriented or irregular slides, export those and combine all the images into a PDF.

I'm sure this will be way faster than battling Node.js. Not sure why I felt I had to write it up.

https://fieldnatsact.com/

Why is #JavaScript so popular? I hate everything about it.

I'm speaking at the #Canberra Field #Naturalists meeting at #ANU next month on #Malaise trapping and the #insects and other #invertebrates that surround us without our noticing them.

I expect most of my slides to be arrays of four or six #microscope images with a header (probably a family name in most cases) and captions for each image.

I don't want to lay out all these images in #LibreOffice (or any similar presentation tool) because I'm a perfectionist and getting it all tidy will take forever.

So, I decided to try out #Slidev, #Marp and other #Markdown-based presentation tools. The Markdown part is very appealing, but they all lean hard into JavaScript. That would be fine so long as I don't have to think about that side of things.

Slidev's AppleBasic theme seemed to be the best starting point, so I started hacking it to add som extra gridded image views. Plain image grids were not too challenging, but I really want captions for each image, so I started trying to understand how the templates use the forest of underlying JS libraries and CSS artefacts to produce the displayed slides.

Frankly, the whole thing is so opaque and would take me much longer to understand than preparing multiple presentations by hand would.

Then I realised I can use #montage on the command line to produce the kind of layouts I want, and I can script #exiftool to extract and prepare the captions which will save time.

So, my new plan is to write a #Python script that processes a #YAML file listing all the slides, titles and image paths. It can generate PNG images that are close to the target 1920*1080 size (give or take a little). I'll then use LibreOffice for a couple of more text-oriented or irregular slides, export those and combine all the images into a PDF.

I'm sure this will be way faster than battling Node.js. Not sure why I felt I had to write it up.

https://fieldnatsact.com/

L'article est intéressant, aussi bien par le concept de l'outil (qui titille en moi une envie de changer Structurizr) que dans sa forme (le style visuel de l'article est dingue) https://www.chiply.dev/post-cn-diagrams #architecture #documentation #diagram #alternatives #yaml #idée

Blog - I had a new bit of learning with Kubernetes Event Driven Autoscaling today

https://piefed.keyboardvagabond.com/c/programming/p/226531/blog-i-had-a-new-bit-of-learning-with-kubernetes-event-driver-autoscaling

Trying out #PyInfra as an alternative to #Ansible. I hate having to program in #YAML so just doing it in pure #python is nice.

So far so good. I was able to install a package, upload some #systemd units, conditionally do a daemon-reload and enable the units with way less thrashing around than I've had with Ansible.

https://pyinfra.com/

#Devops #Automation #ServerConfiguration #Linux

Turns out that not only do Actions runners come with jq preinstalled, but yq is there too.

hollycummins.com/using-yq-in-g…

There was a featured snippet for “is yq available on GitHub actions,” which directed me to a marketplace installer. The yq project itself had a marketplace installer. Clearly, I needed to install it before using it. Right?

My colleague George Gastaldi looked at what I’d done, and pointed out yq was available on the runners. This matters, because we try and limit our use of external, ‘non-official’ actions, for supply chain security reasons.

So I searched again to confirm, and … still found very little. To actually confirm, I had to merge and experiment. And, indeed, the GitHub runners do come with yq pre-installed. They’ve had yq since 2021.

#yaml #yq #jq #GithubActions
#CICD
#ContinuousIntegration
#ContinuousDeployment

Turns out that not only do Actions runners come with jq preinstalled, but yq is there too.

hollycummins.com/using-yq-in-g…

There was a featured snippet for “is yq available on GitHub actions,” which directed me to a marketplace installer. The yq project itself had a marketplace installer. Clearly, I needed to install it before using it. Right?

My colleague George Gastaldi looked at what I’d done, and pointed out yq was available on the runners. This matters, because we try and limit our use of external, ‘non-official’ actions, for supply chain security reasons.

So I searched again to confirm, and … still found very little. To actually confirm, I had to merge and experiment. And, indeed, the GitHub runners do come with yq pre-installed. They’ve had yq since 2021.

#yaml #yq #jq #GithubActions
#CICD
#ContinuousIntegration
#ContinuousDeployment

Turns out that not only do Actions runners come with jq preinstalled, but yq is there too.

hollycummins.com/using-yq-in-g…

There was a featured snippet for “is yq available on GitHub actions,” which directed me to a marketplace installer. The yq project itself had a marketplace installer. Clearly, I needed to install it before using it. Right?

My colleague George Gastaldi looked at what I’d done, and pointed out yq was available on the runners. This matters, because we try and limit our use of external, ‘non-official’ actions, for supply chain security reasons.

So I searched again to confirm, and … still found very little. To actually confirm, I had to merge and experiment. And, indeed, the GitHub runners do come with yq pre-installed. They’ve had yq since 2021.

#yaml #yq #jq #GithubActions
#CICD
#ContinuousIntegration
#ContinuousDeployment

Turns out that not only do Actions runners come with jq preinstalled, but yq is there too.

hollycummins.com/using-yq-in-g…

There was a featured snippet for “is yq available on GitHub actions,” which directed me to a marketplace installer. The yq project itself had a marketplace installer. Clearly, I needed to install it before using it. Right?

My colleague George Gastaldi looked at what I’d done, and pointed out yq was available on the runners. This matters, because we try and limit our use of external, ‘non-official’ actions, for supply chain security reasons.

So I searched again to confirm, and … still found very little. To actually confirm, I had to merge and experiment. And, indeed, the GitHub runners do come with yq pre-installed. They’ve had yq since 2021.

#yaml #yq #jq #GithubActions
#CICD
#ContinuousIntegration
#ContinuousDeployment

Turns out that not only do Actions runners come with jq preinstalled, but yq is there too.

hollycummins.com/using-yq-in-g…

There was a featured snippet for “is yq available on GitHub actions,” which directed me to a marketplace installer. The yq project itself had a marketplace installer. Clearly, I needed to install it before using it. Right?

My colleague George Gastaldi looked at what I’d done, and pointed out yq was available on the runners. This matters, because we try and limit our use of external, ‘non-official’ actions, for supply chain security reasons.

So I searched again to confirm, and … still found very little. To actually confirm, I had to merge and experiment. And, indeed, the GitHub runners do come with yq pre-installed. They’ve had yq since 2021.

#yaml #yq #jq #GithubActions
#CICD
#ContinuousIntegration
#ContinuousDeployment

This weekend's learning activity was figuring out a good way to make k8s templates out of my YAML files. There are a number of ways to do this, including from Ansible or Helm, but after looking at Kustomize, that's the best way for me to go.

Ansible could do it by either:
a) native k8s modules in ansible
b) with YAML files, and the template function, which would just do variable substitution

Helm is extremely overkill for my use case, although I'm sure I could get it to cooperate.

Kustomize is the best mix of $inputFiles + modifications = $outputFiles per environment, and I really like how it works.

You define your top level YAML files and then tell the environments in an overlays/ directory how you want things to change. You can even have it apply a namespace to all resources in there so it's never forgotten or replace values such as ingress hostnames, which have to be unique per env anyways.

This will let me write one set of files and then push the YAML to k8s properly. I also fully intend to use this for a DR kind of situation where I need to recover everything.

All of this will fit very well into my new Gitea instance, replete with an Actions runner.

#homelab #k8s #kubernetes #kustomize #learning #neverstoplearning #technology #yaml #selfhosted

@rl_dane I saw this just before sleep

I tried with #Fish

Fish store history as #YAML

I tweaked the command to make it barely works

Since it's YAML, it's store the timestamps

So, i tried to do an actual #year_in_review

3 hours later, here it is !

https://gitlab.com/pinage404/dotfiles/-/commit/5089def105806afe92684609a004081cf5aa136d

#FishShell #Fish_Shell #Recap #Rewind

🔐 #SOPS: Secrets OPerationS - simple & flexible tool for managing secrets #devops #security #opensource #infosec

🔑 Encrypts #YAML, #JSON, ENV, INI & binary files with multiple encryption backends: #AWS KMS, #GCP KMS, Azure Key Vault, #age & #PGP

🛡️ Only encrypts values while leaving keys in cleartext for easy diffing & version control in #git repositories

🔄 Key groups with Shamir's Secret Sharing - split data keys requiring multiple identities to decrypt

🧵 👇

🔐 #SOPS: Secrets OPerationS - simple & flexible tool for managing secrets #devops #security #opensource #infosec

🔑 Encrypts #YAML, #JSON, ENV, INI & binary files with multiple encryption backends: #AWS KMS, #GCP KMS, Azure Key Vault, #age & #PGP

🛡️ Only encrypts values while leaving keys in cleartext for easy diffing & version control in #git repositories

🔄 Key groups with Shamir's Secret Sharing - split data keys requiring multiple identities to decrypt

🧵 👇

🔐 #SOPS: Secrets OPerationS - simple & flexible tool for managing secrets #devops #security #opensource #infosec

🔑 Encrypts #YAML, #JSON, ENV, INI & binary files with multiple encryption backends: #AWS KMS, #GCP KMS, Azure Key Vault, #age & #PGP

🛡️ Only encrypts values while leaving keys in cleartext for easy diffing & version control in #git repositories

🔄 Key groups with Shamir's Secret Sharing - split data keys requiring multiple identities to decrypt

🧵 👇

🔐 #SOPS: Secrets OPerationS - simple & flexible tool for managing secrets #devops #security #opensource #infosec

🔑 Encrypts #YAML, #JSON, ENV, INI & binary files with multiple encryption backends: #AWS KMS, #GCP KMS, Azure Key Vault, #age & #PGP

🛡️ Only encrypts values while leaving keys in cleartext for easy diffing & version control in #git repositories

🔄 Key groups with Shamir's Secret Sharing - split data keys requiring multiple identities to decrypt

🧵 👇

🔐 #SOPS: Secrets OPerationS - simple & flexible tool for managing secrets #devops #security #opensource #infosec

🔑 Encrypts #YAML, #JSON, ENV, INI & binary files with multiple encryption backends: #AWS KMS, #GCP KMS, Azure Key Vault, #age & #PGP

🛡️ Only encrypts values while leaving keys in cleartext for easy diffing & version control in #git repositories

🔄 Key groups with Shamir's Secret Sharing - split data keys requiring multiple identities to decrypt

🧵 👇

So, in order to do the cleanups, I can use `yq`'s excellent filtering abilities. For example I have a list of verbatim API endpoints like `/token` and `/endpoint/{id}` in `allowed_apis.lst`:

```
yq '(load_str("allowed_apis.lst") | split("\n")) as $l | .paths |= with_entries(select(.key as $k | $l | any_c(. == $k)))' api.yaml > api_cleaned_paths.yaml
```

And similar approach for models, except for `any_c(..)` I have to use `all_c(. != $k)`.

#openapi #yq #yaml #openapigenerator

**Duper's new superpowers!**

It's been over a month since Duper's public announcement, and now, it's more super than ever! I've taken all the feedback from the initial post and worked on it. With Temporal values, support for more languages, extra tools for logging, a fully-functioning LSP, and more, it's certainly not pulling any punches!

https://duper.dev.br/blog/duper-s-new-superpowers.html

#rust #rustlang #dotnet #node #javascript #wasm #python #json #yaml #toml

**Duper's new superpowers!**

It's been over a month since Duper's public announcement, and now, it's more super than ever! I've taken all the feedback from the initial post and worked on it. With Temporal values, support for more languages, extra tools for logging, a fully-functioning LSP, and more, it's certainly not pulling any punches!

https://duper.dev.br/blog/duper-s-new-superpowers.html

#rust #rustlang #dotnet #node #javascript #wasm #python #json #yaml #toml