# YAML Published articles for YAML. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to build a Language Server Protocol (LSP) plugin for Claude Code DevFeed: [How to build a Language Server Protocol (LSP) plugin for Claude Code]() Original publisher: [Read original article]() Author: Roger Winter Published: 2026-09-17T07:00:00Z Content type: tutorial Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [Claude Code](), [CircleCI](), [Protocol (disambiguation)](), [YAML](), [CI/CD](), [Code]() Tags: [ai-development](), [ci-cd](), [circleci](), [claude-code](), [code](), [how-to](), [protocol](), [yaml]() ### AI overview This tutorial explains how to wrap CircleCI's open-source YAML language server as a Claude Code plugin. The plugin provides real-time diagnostics, hover guidance, and best-practice feedback while Claude edits CircleCI configuration files. The article also discusses the implementation, reuse with other language servers, and a benchmark against editing without that feedback, while noting that the example plugin is unofficial and unsupported. ### Source excerpt Build custom Claude Code plugins to wrap the CircleCI language server. Improve your CI/CD configs with real-time diagnostics and best-practice guidance. ## Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator DevFeed: [Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator]() Original publisher: [Read original article]() Author: Anil Joshi Published: 2026-09-17T06:43:32Z Content type: tutorial Language: en Sources: [Blog - Percona]() Topics: [Replication](), [export](), [Percona Server for MySQL](), [configuration](), [Server](), [Kubernetes](), [Database]() Tags: [cloud](), [configuration](), [database-trends](), [featured](), [innodb-clusterset](), [insight-for-dbas](), [kubernetes](), [kubernetes-operators](), [mysql](), [mysql-group-replication](), [mysql-high-availability](), [mysql-replication](), [open-source](), [operator](), [percona-kubernetes-operators](), [percona-operator-for-mysql](), [percona-server-for-mysql](), [percona-software](), [replication](), [uncategorized](), [yaml]() ### AI overview This tutorial explains how to configure cross-site replication between two Percona Operator for MySQL clusters to create a ClusterSet environment for disaster recovery and switchover between data-center and disaster-recovery members. It covers deploying the clusters, retrieving endpoints and cluster names, transferring credentials, and initializing the DR cluster. ### Source excerpt A while ago, we discussed the cross-site replication feature of the Percona PXC operator. Recently, a similar cross-site replication feature was introduced in the Percona (PS MySQL) operator v1.2.0, a topology based on Group Replication/InnoDB Cluster. In this blog post, we will explore how to add a DR Cluster to an existing DC Cluster to ... Continued The post Group Replication Beyond a Single Cluster: DC-DR with Percona (PS MySQL) Operator appeared first on Percona. ## Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next DevFeed: [Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next]() Original publisher: [Read original article]() Author: Abhijit Pujare Eric Minick Published: 2026-09-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [policy-as-code](), [Open Policy Agent](), [rego](), [Kyverno](), [Software Engineering](), [Kubernetes](), [JSON](), [YAML](), [AI Agent]() Tags: [ai-agent](), [compliance](), [json](), [kyverno](), [opa](), [open-policy-agent](), [policies](), [policy-as-code](), [rego](), [security](), [software-engineering](), [yaml]() ### AI overview This article surveys the 2026 Policy as Code ecosystem, comparing general-purpose Open Policy Agent and Rego with specialized approaches such as Kyverno, Cedar, and agent-oriented governance. It discusses the shift toward automated, machine-readable governance, the separation of policy from business logic, and the challenges of authoring and maintaining Rego as schemas evolve. ### Source excerpt | Blog ## The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies DevFeed: [The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-09-08T03:00:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [Kubernetes](), [Network](), [Security](), [Zero Trust](), [Architecture & Design]() Tags: [blog](), [cni](), [container](), [guide](), [how-to](), [ingress](), [kubernetes](), [network](), [network-security](), [postgersql](), [security](), [test](), [yaml](), [zero-trust]() ### AI overview A hands-on lab for implementing zero-trust network segmentation in Kubernetes with NetworkPolicies. It demonstrates default-deny rules, label-based ingress and egress permissions, DNS access, external API restrictions, and traffic validation in a three-tier frontend, backend, and PostgreSQL architecture enforced by Calico. ### Source excerpt This blog is a deep walkthrough about network policies in Kubernetes, read to know more. The post The Default Deny Dilemma: A Practical Guide to Kubernetes Network Policies appeared first on CYBERTEC PostgreSQL | Services & Support. ## Configuring Guix services by translating Scheme fields to YAML DevFeed: [Configuring Guix services by translating Scheme fields to YAML]() Original publisher: [Read original article]() Author: Sergio Pastor Pérez Published: 2026-09-07T08:30:00Z Content type: tutorial Language: en Sources: [GNU Guix -- Blog]() Topics: [configuration](), [YAML](), [OpenSSH]() Tags: [configuration](), [development](), [functional-package-management](), [how-to](), [openssh](), [programming-interfaces](), [scheme-api](), [yaml]() ### AI overview This tutorial explains how Guix services represent configuration through Scheme bindings and how to define a complex Goimapnotify service configuration by translating Guile Scheme fields into YAML. ### Source excerpt Guix system and Guix home introduce the concept of services. These provide users with a way to control background processes, commonly refereed as daemons , as well as ways of controlling the setup of files. For example, openssh-service-type is a service which controls a SSH daemon. In contrast, etc-service-type is a service that populates the contents of the /etc directory. One peculiarity of Guix services is that it's customary to provide Scheme bindings for the different fields. By that I mean that the different fields of the configuration of most services will be a... ## Mobile UI Testing with Claude Code, Cursor and Codex DevFeed: [Mobile UI Testing with Claude Code, Cursor and Codex]() Original publisher: [Read original article]() Author: Ashish Kharche Published: 2026-09-01T10:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [Testing](), [Mobile](), [Model Context Protocol](), [Android](), [iOS](), [Emulator](), [simulator]() Tags: [agent](), [android](), [chromium](), [claude-code](), [cli](), [codex](), [cursor](), [emulator](), [ios](), [maestro](), [mcp](), [mobile](), [regression](), [simulator](), [testing](), [yaml]() ### AI overview This tutorial explains how Claude Code, Cursor, Codex, and other MCP-enabled coding agents can use Maestro MCP to explore mobile app interfaces on iOS Simulators, Android emulators, physical Android devices, and Chromium, then save the tested steps as reusable Flow files. The saved Flows can be rerun through an agent or the CLI, including in CI, to detect UI changes. ### Source excerpt Have Claude Code, Cursor or Codex run a UI test on an iOS Simulator or Android emulator, then save it as a Flow and run the same test again. ## Maestro CLI 2.9.0: test light and dark mode in one flow DevFeed: [Maestro CLI 2.9.0: test light and dark mode in one flow]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-08-31T15:00:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Command-line interface](), [Mobile](), [WebView](), [Web](), [Chrome](), [YAML]() Tags: [2-9-0](), [android](), [angular](), [chrome](), [cli](), [dark-mode](), [ios](), [react](), [release](), [vue](), [web](), [webview](), [yaml]() ### AI overview Maestro CLI 2.9.0 adds commands for testing light and dark themes within a single flow across iOS, Android, and Web. It also introduces negation globs for YAML files and improves Android WebView inspection, Chrome Web flows, Android reliability, and upload-status polling. ### Source excerpt Maestro CLI 2.9.0 adds dark-mode commands for iOS, Android, and Web, negation globs in config.yaml, and reliability work for Android WebViews and modern Chrome. ## How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD DevFeed: [How Developers Can Test Their Feature Branch Against Various Playwright Configurations Before Creating a Merge Request in GitLab CI/CD]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-28T20:18:08Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [GitLab](), [CI/CD](), [Playwright](), [YAML](), [Development]() Tags: [bun-create-playwright](), [chromium](), [ci-cd](), [firefox](), [gitlab](), [gitlab-ci](), [playwright](), [tests](), [yaml]() ### AI overview This tutorial shows how to configure a GitLab CI/CD pipeline so developers can test a feature branch before creating a merge request. It uses spec inputs in a YAML configuration to let users choose the branch, Playwright test suite, and browser, including Chromium, Firefox, WebKit, or all browsers. ### Source excerpt Developers need the option to test out their feature branch before merging it into main. In the last section, we set up a GitLab CI/CD Pipeline in our bun-create-playwright project to check every GitLab Merge Request. Now, we will be giving developers option to create a new pipeline where they can choose: Which feature branch to test against. Which test suite to execute (LoginPage tests? Secure Area? Or all of them?) Which Playwright browser to use: Chromium, Firefox, WebKit, or all. All these features can be set up using our .gitlab-ci.yaml file! Go to to bun-create-playwright, view the Pipelines section, and select the New Pipeline button. Run a New Bun-Create-Playwright Pipeline If you go to the Run new pipeline page at https://gitlab.com/tjmaher/bun-create-playwright/-/pipelines/new you can see the following default values I've set: https://gitlab.com/tjmaher/bun-create-playwright/-/pipelines/new By default: Branch name is "main", TEST_SUITE is "all", BROWSER is "all". ... But all these values can be set, with the developer choosing the options laid out in the .gitlab-ci.yaml file. Collect User Data With Spec Inputs We are going to be adding to the GitLab Pipeline we built in our last post Setting up a CI/ CD pipeline with GitLab: Quality, Test and Report. First, we are going to add a "spec" section to the header of the YAML file to define the behavior of a pipeline, and within that spec header, we will ask the person who triggered a new pipeline to set user defined inputs for the pipeline. spec: inputs: browser: description: "Browser project to run against." default: "all" options: ["all", "chromium", "firefox", "webkit"] suite: description: "Select full regression suite, or a single spec" default: "all" options: ["all", "login.spec.ts", "secure-area.spec.ts"] This is where we declare the "browser" and "suite" variables that appear when a user creates a new pipeline. We've given them a choice to run their feature branch code against: Browser: All, Chromium, Fir ## Pulumi Kubernetes v4.34.0: CRDs as provider extensions DevFeed: [Pulumi Kubernetes v4.34.0: CRDs as provider extensions]() Original publisher: [Read original article]() Author: Guinevere Saenger Published: 2026-08-28T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Kubernetes](), [Extension](), [SDKs](), [YAML](), [ingress-nginx]() Tags: [extensions](), [install](), [kubernetes](), [migration](), [product](), [providers](), [release](), [releases](), [sdk](), [sdks](), [yaml]() ### AI overview Pulumi Kubernetes provider v4.34.0 adds support for extending the provider with Kubernetes Custom Resource Definitions through a manifest and the new --extension flag. The release generates SDKs, supports all supported Pulumi languages including YAML, uses a single provider instance, and provides a migration path from crd2pulumi. ### Source excerpt We're really excited to bring you v4.34.0, the newest version of the Pulumi Kubernetes provider, which includes improved support for Kubernetes Custom Resource Definitions (CRDs). As with any release, we've also shipped standard dependency updates and bug fixes. This provider release includes the newest resources for Kubernetes v1.37.0, which was recently cut. So that in itself is very exciting! But the feature we're proudest of is that you can now extend the Kubernetes provider with any Kubernetes Custom Resource Definition of your choice by passing its manifest file to Pulumi, using the new --extension flag. We believe first-class CRD support in Pulumi is becoming more important than ever. For example, since the retirement of the ingress-nginx controller earlier this year, the recommended path for cluster ingress is Gateway API, which is maintained and shipped as CRDs. Generating a Pulumi SDK for CRDs In your Pulumi project root, run: pulumi package add kubernetes --extension "name=gateway-networking crd-manifest=gateway-api-crds.yaml" You will see the custom SDK appear in a new sdks/ folder, as well as a new parameterization reference in Pulumi.yaml. Single provider instance Your new CRD schema exists as an extension to your existing provider and will be managed under the same provider instance, allowing you to use a single provider configuration and kubeconfig. SDKs as dependencies Additionally, your code no longer needs to ship SDK files as part of the project. The provider extension is referenced in your project file and its SDK, like all dependencies, can be regenerated via pulumi install. You can choose to version the extension SDK, or continue to check the files into version control if you so desire. Full language support, including for YAML Kubernetes CRDs can now be provisioned with Pulumi in all supported languages. Unified CLI experience pulumi package add --extension extends your CRD schema into the Pulumi Kubernetes provider, using the same CLI as any ## Highly Available PostgreSQL on Kubernetes in 10 Minutes DevFeed: [Highly Available PostgreSQL on Kubernetes in 10 Minutes]() Original publisher: [Read original article]() Author: Hans-Jürgen Schönig Published: 2026-08-18T05:07:31Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [PostgreSQL](), [Kubernetes](), [postgresql clusters](), [Database](), [Replication]() Tags: [failover](), [health-checks](), [how-to](), [kubernetes](), [operator](), [patroni](), [pg-operator](), [postgresql](), [postgresql-on-cloud](), [replication](), [tutorial](), [yaml]() ### AI overview This tutorial demonstrates how to deploy a highly available PostgreSQL cluster on Kubernetes with the CYBERTEC PG Operator. Using a 14-line YAML configuration on minikube, it shows leader election, streaming replication, health checks, automatic failover, and read-only replica behavior. It also explains how anti-affinity must be disabled for the single-node minikube setup but should remain enabled on multi-node production clusters. ### Source excerpt This is a detailed blog post about PostgreSQL in Kubernetes, using PG Operator. The post Highly Available PostgreSQL on Kubernetes in 10 Minutes appeared first on CYBERTEC PostgreSQL | Services & Support. ## Coding Challenge #131 - Automated Code Review Agent DevFeed: [Coding Challenge #131 - Automated Code Review Agent]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-08-15T08:01:51Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [GitHub Copilot code review](), [pull-requests](), [Pull Request](), [Orchestration](), [GitHub](), [Artificial Intelligence](), [YAML](), [engineering-culture]() Tags: [agent](), [ai](), [automated](), [code-review](), [coding](), [collaboration](), [github](), [orchestration](), [pull-request](), [run](), [tools](), [triggers](), [workflow](), [yaml]() ### AI overview Coding Challenge #131 asks readers to build an automated code review agent that reviews pull requests against team coding guidelines and posts findings as comments. The challenge covers retries, event triggers, concurrency control, large pull requests, static analysis tools, and lookup capabilities. ### Source excerpt This challenge is to build your own code review agent. ## Introducing the Guardener GitHub App DevFeed: [Introducing the Guardener GitHub App]() Original publisher: [Read original article]() Published: 2026-08-12T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard actions](), [GitHub](), [CI/CD](), [migration](), [Security](), [Open Source]() Tags: [chainguard](), [chainguard-actions](), [ci-cd](), [github](), [migration](), [open-source](), [pull-request](), [security](), [yaml]() ### AI overview Chainguard introduces the Guardener GitHub app in beta to automate migration from GitHub Actions to secure-by-default Chainguard Actions. The app helps teams inventory actions across repositories and open migration pull requests for actions with Chainguard equivalents, improving CI/CD security with less developer friction. ### Source excerpt Meet the Guardener GitHub app, built to automate migration to hardened Chainguard Actions and help teams secure CI/CD without slowing developers. ## Deploy MCP Servers on AWS Lambda with Serverless Framework v4 DevFeed: [Deploy MCP Servers on AWS Lambda with Serverless Framework v4]() Original publisher: [Read original article]() Author: Serverless Team Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [MCP](), [AWS Lambda](), [serverless framework](), [Streaming]() Tags: [aws](), [aws-lambda](), [cloud-computing](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [mcp](), [news](), [pricing](), [serverless](), [serverless-architecture](), [serverless-framework](), [streaming](), [yaml]() ### AI overview A Serverless Framework v4.41.0 deployment workflow for MCP servers on AWS Lambda, using YAML and providing an HTTPS endpoint, response streaming, and pay-per-request pricing. ### Source excerpt Serverless Framework v4.41.0 deploys MCP servers to AWS Lambda in a few lines of YAML - a real HTTPS endpoint, response streaming, and pay-per-request pricing. ## Generating AI Descriptions of Automated Pull Requests DevFeed: [Generating AI Descriptions of Automated Pull Requests]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Daniel Doubrovkine]() Topics: [GitHub Copilot CLI](), [GitHub Actions](), [GitHub Copilot](), [Large Language Model](), [Ruby](), [Slack](), [changelog](), [Pull Request](), [Open Source](), [JSON](), [YAML]() Tags: [ai](), [automated](), [changelog](), [ci](), [cli](), [copilot](), [github](), [github-actions](), [github-copilot](), [github-copilot-cli](), [json](), [llm](), [open-source](), [pull-request](), [pull-requests](), [ruby](), [yaml]() ### AI overview A tutorial explains how the maintainer of the slack-ruby-client library uses a scheduled GitHub Actions workflow and GitHub Copilot CLI to generate meaningful commit messages, pull request bodies, and CHANGELOG entries from diffs of regenerated Slack API code. It also covers YAML indentation, prompt files, response logging, and extracting a JSON result from Copilot CLI output. ### Source excerpt The slack-ruby-client library, an open source Ruby gem I maintain, runs a scheduled GitHub Actions workflow that regenerates code from Slack's API definitions and opens a pull request with the diff. The commit message and CHANGELOG entry used to be a generic "Update API (2026-08-11)", which told a reviewer nothing about what actually changed. Here's how we taught the workflow to describe its own diffs, using GitHub Copilot CLI, which open source maintainers can get for free. The Idea The workflow already computes a diff before opening the pull request. Instead of a boilerplate commit message, we pipe that diff through an LLM and ask it to summarize what changed, then use the response as the commit message and PR body. - name: Check for changes id: changes run: | if git diff --quiet; then echo "changed=false" >> "$GITHUB_OUTPUT" else echo "changed=true" >> "$GITHUB_OUTPUT" fi - name: Prepare diff for AI summary if: steps.changes.outputs.changed == 'true' run: | git diff --stat | sed 's/^/ /' > /tmp/diff_stat.txt git diff | head -c 20000 | sed 's/^/ /' > /tmp/diff.txt The sed 's/^/ /' indent isn't decorative. actions/ai-inference substitutes template variables as raw text into a prompt YAML file before parsing it, so a multi-line diff starting at column 0 breaks the indentation of the enclosing content: |- block scalar. Pre-indenting the file to match keeps the YAML valid no matter what the diff looks like. The Prompt File actions/ai-inference supports .prompt.yml files, a small convention for keeping the system/user prompt out of the workflow YAML. messages: - role: system content: |- You write CHANGELOG entries describing an automated API update to slack-ruby-client, a Ruby gem whose Web API endpoint methods, argument validations, specs, and bin commands are code-generated from vendored Slack API method definitions (via a git submodule and rake task). Given a diffstat and a diff of the regenerated files, respond with ONLY a single JSON object (no markdown code fence ## YAML for DevOps Beginners, Syntax, Rules and Common Mistakes DevFeed: [YAML for DevOps Beginners, Syntax, Rules and Common Mistakes]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-06T17:16:19Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [YAML](), [configuration](), [DevOps](), [Ansible](), [ci](), [Kubernetes]() Tags: [ansible](), [block-scalars](), [ci-cd](), [cloud](), [configuration](), [devops](), [errors](), [guide](), [how-to](), [json](), [kubernetes](), [kubernetes-yaml-manifests](), [linter](), [mistakes](), [multi-document-yaml](), [structure](), [syntax](), [validation](), [yaml](), [yaml-anchors-and-aliases](), [yaml-common-mistakes](), [yaml-for-devops](), [yaml-indentation-rules](), [yaml-norway-problem](), [yaml-syntax-rules](), [yaml-vs-json](), [yamllint-validation]() ### AI overview A tutorial explaining YAML syntax, implicit typing, indentation rules, block scalars, anchors, aliases, and merge keys. It emphasizes that YAML can silently reinterpret unquoted values and recommends linting and schema validation in CI pipelines. ### Source excerpt YAML tries to guess what you meant, and that is the entire problem. Once you know which values it silently reinterprets and why, the manifests that mysteriously break stop being mysterious. ## Как мы вынесли алгоритм ценообразования из кода Яндекс Такси (и почему это не было очевидно с самого начала) DevFeed: [Как мы вынесли алгоритм ценообразования из кода Яндекс Такси (и почему это не было очевидно с самого начала)]() Original publisher: [Read original article]() Author: glebf123321 (Яндекс) Published: 2026-08-05T07:05:00Z Content type: article Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [яндекс]() Tags: [c-plus-plus](), [tag-1e4ee1f65f5a](), [tag-3670787a9009](), [tag-4004cf5948d3](), [tag-8fc3b37d0ab6](), [yaml]() ### AI overview Yandex describes how it extracted the Yandex Taxi pricing algorithm from service code. The article covers pricing across the ride lifecycle, why a ready-made scripting language was not used, the price-transformation chain, and the need for a formal verifier. ### Source excerpt Когда вы открываете Яндекс Go для заказа такси и вводите адрес, приложение за доли секунды показывает цену. Кажется, что это несложно: Кажется, что это несложно: взять расстояние и время в пути, умножить их на значения из тарифа. На самом деле, за этой ценой стоит не один десяток факторов -- например, скидки, спрос, геозоны. И это ещё без учёта того, что пассажир взял с собой кота или лыжи. В этой статье -- о том, как мы вынесли алгоритм ценообразования из кода сервиса, почему не взяли готовый скриптовый язык, что такое цепочка преобразований цены и зачем нам понадобился формальный верификатор. Читать далее ## Announcement: Xcode16 Deprecation in Semaphore DevFeed: [Announcement: Xcode16 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-08-04T13:47:48Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [macOS](), [ci]() Tags: [announcement](), [ci](), [deprecated](), [end-of-life](), [lifecycle](), [macos](), [operating-systems](), [product-news](), [yaml]() ### AI overview Semaphore is deprecating and retiring its macOS Xcode16 build environments. Brownout periods will run from September 7 through October 4, 2026, before the environments are removed on October 5, 2026. Users are instructed to migrate pipelines to macos-xcode26 and validate them. ### Source excerpt MacOS Xcode16 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode16 build environments. Semaphore users should switch to Xcode26. Why We're Deprecating Xcode16 As operating systems age, they cease to receive timely security [...] The post Announcement: Xcode16 Deprecation in Semaphore appeared first on Semaphore. ## Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG) DevFeed: [Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG)]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-08-04T05:00:38Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [configuration](), [PostgreSQL](), [postgresql clusters](), [Kubernetes](), [GitOps](), [YAML](), [kubectl]() Tags: [administration](), [cloudnativepg](), [configuration](), [configuration-management](), [gitops](), [how-to](), [kubectl](), [kubernetes](), [postgresql](), [replication](), [yaml]() ### AI overview This tutorial explains how CloudNativePG manages PostgreSQL configuration in Kubernetes. It contrasts imperative editing of configuration files with declarative management through Kubernetes YAML and shows how to define database parameters and pg_hba.conf rules in a CNPG cluster resource. ### Source excerpt This blog talks about Configuration Management in PostgreSQL with CNPG, with some great examples in a comprehensive way. The post Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG) appeared first on CYBERTEC PostgreSQL | Services & Support. ## What is Ansible? DevFeed: [What is Ansible?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-23T18:25:09Z Content type: tutorial Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Ansible](), [Automation](), [configuration](), [Network](), [Open Source](), [ssh](), [YAML](), [Server]() Tags: [ansible](), [applications](), [automation](), [configuration](), [faq](), [network](), [open-source](), [servers](), [ssh](), [tasks](), [yaml]() ### AI overview Ansible is an open-source, agentless IT automation tool for configuring systems, deploying applications, and managing network devices. It uses human-readable YAML playbooks and connects through SSH to automate repetitive changes across routers, switches, and servers. ### Source excerpt Ansible is an open-source IT automation tool that configures systems, deploys applications, and manages network devices using simple, human-readable YAML files called playbooks. It's agentless, connecting via SSH, and widely used by network engineers to automate repetitive tasks like configuration changes across routers, switches, and servers at scale. ## kPointer Replaces cw-json with Support for JSON, YAML, HTML, and XML DevFeed: [kPointer Replaces cw-json with Support for JSON, YAML, HTML, and XML]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-22T12:27:15Z Content type: release Language: en Sources: [The CommonsBlog]() Topics: [data](), [JSON](), [YAML](), [HTML](), [XML](), [Command-line interface](), [test]() Tags: [blog](), [cli](), [data](), [html](), [json](), [sdk](), [test](), [testing](), [xml](), [yaml]() ### AI overview kPointer replaces cw-json as a library for extracting values from structured data. It supports JSON, YAML, HTML, and XML through adapter-style abstractions, adds JavaScript access path notation, and includes conformance testing and a CLI. ### Source excerpt The cw-json project has been replaced by kPointer -- learn what kPointer offers! ## How to Troubleshoot and Debug Ansible Playbooks DevFeed: [How to Troubleshoot and Debug Ansible Playbooks]() Original publisher: [Read original article]() Author: Mrinalini Sugosh Published: 2026-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Ansible](), [debugging](), [Infrastructure as code](), [YAML]() Tags: [ansible](), [debugging](), [how-to](), [iac](), [infrastructure-as-code](), [troubleshooting](), [yaml]() ### AI overview This tutorial explains how to troubleshoot and debug Ansible playbooks. It covers structured and conditional debugging, verbosity controls, targeted variable inspection, reusable debugging roles, failure taxonomies, and CI/CD-friendly logging. It also describes common problems such as syntax errors, variable conflicts, connection errors, and inconsistent execution across hosts. ### Source excerpt Master how to debug Ansible with expert tips for troubleshooting playbooks. Learn structured debugging, reduce errors, and streamline Infrastructure Deployments | Blog ## OpenTelemetry Spring Boot Starter Adds Declarative YAML Configuration in Version 2.26.0 DevFeed: [OpenTelemetry Spring Boot Starter Adds Declarative YAML Configuration in Version 2.26.0]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-14T07:47:36Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [Spring Boot](), [YAML](), [configuration](), [Environment Variables](), [telemetry](), [tracing]() Tags: [configuration](), [environment](), [java](), [opentelemetry](), [schema](), [setup](), [spring-boot](), [telemetry](), [traces](), [yaml]() ### AI overview The article explains how declarative configuration in the OpenTelemetry Spring Boot starter, available from version 2.26.0, embeds the SDK's YAML schema in application.yaml. It contrasts this approach with environment-variable configuration and describes how the YAML schema can represent telemetry pipelines and options beyond the fixed environment-variable catalog. ### Source excerpt The OpenTelemetry Spring Boot starter gained declarative-configuration support starting in version 2.26.0 -- the same YAML schema the Java agent introduced in late 2025, now embedded inside application.yaml. This post traces what one env var, OTEL_SERVICE_NAME=petclinic, does in that new world, and where the seams are. In a hurry? Jump straight to the Spring Boot starter declarative-config docs, paste your application.properties into the interactive converter, or pick your SDK setup in the Ecosystem Explorer with the Spring Boot starter target selected. Come back for the story when you have a coffee. ## Rebuilding the CircleCI CLI from scratch DevFeed: [Rebuilding the CircleCI CLI from scratch]() Original publisher: [Read original article]() Author: Pete Steyert-Woods Published: 2026-07-07T16:00:00Z Content type: article Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [Command-line interface](), [Go Language](), [MCP Server](), [OAuth](), [Text-based user interface](), [debugging](), [telemetry](), [configuration](), [YAML](), [AI-assisted coding]() Tags: [ai-development](), [ci](), [circleci-cli](), [cli](), [coding-agents](), [configuration](), [debugging](), [developer-tools](), [go](), [mcp](), [mcp-server](), [oauth](), [terminal](), [yaml]() ### AI overview CircleCI rebuilt its CLI from scratch in Go, focusing on human-first terminal output, predictable JSON, stable exit codes, browser OAuth login, debugging features, and an MCP server for coding agents. ### Source excerpt We rebuilt the CircleCI CLI from the ground up in Go: human-first output, -json everywhere, browser OAuth login, a built-in debugging TUI, and an MCP server for your coding agent. ## Stream Oracle changes to ClickHouse in real time DevFeed: [Stream Oracle changes to ClickHouse in real time]() Original publisher: [Read original article]() Author: Prakhar Garg Published: 2026-07-07T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [clickhouse](), [Redpanda-Connect](), [Oracle Database](), [Kafka](), [real-time](), [data](), [Database](), [YAML]() Tags: [clickhouse](), [connectors](), [data](), [database](), [event](), [integration](), [kafka](), [oracle](), [pipeline](), [real-time](), [redpanda-connect](), [schema](), [yaml]() ### AI overview A hands-on walkthrough shows how to stream Oracle change data capture events through Redpanda Connect into ClickHouse in real time. It uses Oracle LogMiner and YAML-configured pipelines, with a Redpanda topic serving as an intermediate store before data is delivered to ClickHouse or other destinations. ### Source excerpt A hands-on walkthrough of the new Oracle input in Redpanda Connect. No Debezium, no Kafka Connect runtime, no JVM. [Next page]()