Render rich text, tables, progress bars, syntax highlighting,
markdown and more to the terminal.

Stable branch of the Chef 14 packages.

Chef is an open source systems integration framework built to bring the benefits of configuration management to your entire infrastructure. You write source code to describe how you want each part of your infrastructure to be built, then apply those descriptions to your servers. The result is a fully automated infrastructure: when a new server comes on line, the only thing you have to do is tell Chef what role it should play in your architecture.

Development project for the latest Chef version. In our approach to make Chef a part of openSUSE, the development of the Chef 11 core packages now happens mostly in the appropriate project, devel:languages:erlang.

Chef is an open source systems integration framework built to bring the benefits of configuration management to your entire infrastructure. You write source code to describe how you want each part of your infrastructure to be built, then apply those descriptions to your servers. The result is a fully automated infrastructure: when a new server comes on line, the only thing you have to do is tell Chef what role it should play in your architecture.

Everything related to Jetporch, Michael deHaan's new project (he is the original creator of Ansible...)

Jetporch - the Jet Enterprise Professional Orchestrator

Jetporch (aka Jet) is a general-purpose, community-driven IT automation platform for configuration management, deployment, orchestration, patching, and arbitrary task execution workflows.

Created and run by the creator of Ansible.

Packages related to opentofu, the open source fork of terraform

Fork of Terraform

OpenTofu is an OSS tool for building, changing, and versioning infrastructure safely and efficiently. OpenTofu can manage existing and popular service providers as well as custom in-house solutions.

The key features of OpenTofu are:
- Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
- Execution Plans: OpenTofu has a "planning" step where it generates an execution plan. The execution plan shows what OpenTofu will do when you call apply. This lets you avoid any surprises when OpenTofu manipulates infrastructure.
- Resource Graph: OpenTofu builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, OpenTofu builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
- Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what OpenTofu will change and in what order, avoiding many possible human errors.

Packaging terraform and different external providers

Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.

What's this for?

When you need to see the output from all changed files within a directory.

Why doesn't tail -f /var/logs/* work?

Unfortunately, tail -f /logs/* may not do what you want it to do. Bash will expand * to all existing files within /logs/ and then show the extra lines added to each of them.

It also will not recurse down, any levels deeper than the current directory.

How is fstail different then?

fstail uses the gopkg.in/fsnotify to detect both new files, and existing files that are changed. It then starts concatenting their contents to the terminal.

I needed this for actuated.dev which launches microVMs on servers for CI.

Each VM launched will create a different file at: /var/log/actuated/GUID.txt, and tail -f * would only find existing files.

Firecracker is a virtualization technology for creating and managing
multi-tenant container and function-based services.

firectl is a command-line tool to run Firecracker microVMs

This project is where work on new versions for packages related to containers, like docker, runc, etc. is being done. This project contains the packages as well as the runtime dependencies. Thus, feel free to add this repo to your box and install the packages you are interested in.

Some build time dependencies are on other projects that we use on "build time", like go packages. If you are interested on knowing where each build dependency comes from, use "osc buildinfo".

Some packages here are automatically submitted to openSUSE:Factory.

Feel free to fork the packages here and send submit requests with patches/updates.

Diun is a CLI application written in Go and delivered as a single executable (and a Docker image) to receive notifications when a Docker image is updated on a Docker registry.

Docker Compose is a tool for running multi-container applications on Docker defined using the Compose file format. A Compose file is used to define how the one or more containers that make up your application are configured. Once you have a Compose file, you can create and start your application with a single command: docker compose up.
About update and backward compatibility

Docker Compose V2 is a major version bump release of Docker Compose. It has been completely rewritten from scratch in Golang (V1 was in Python). The installation instructions for Compose V2 differ from V1. V2 is not a standalone binary anymore, and installation scripts will have to be adjusted. Some commands are different.

For a smooth transition from legacy docker-compose 1.xx, please consider installing compose-switch to translate docker-compose ... commands into Compose V2's docker compose .... . Also check V2's --compatibility flag.

Compose Switch is a replacement to the Compose V1 docker-compose (python) executable. It translates the command line into Compose V2 docker compose then run the latter.