The Wayback Machine - https://web.archive.org/web/20210704210835/https://github.com/topics/infrastructure-automation
Skip to content
#

infrastructure-automation

Here are 62 public repositories matching this topic...

jouve
jouve commented Jun 3, 2021

Description

let's say I have an apache process group I want to control.

  • when using supervisord.running, the name must be apache:* (which is the same notation used by supervisor)
  • when using supervisord.dead, the name must be apache: (without the *)

As both states mirror each other, I expect them to use the same convention for name, the one from running since it

'Fortosi' Kubernetes extension is meant to address a fundamental requirement of any project team running their applications on Kubernetes - which is to quickly provision CI/CD pipelines (on demand) for their various private/public GitHub projects/organisation using simple kubectl commands. Basically, implementing the concept of No Ops. It is agnostic of cloud platform, be it AWS (EKS) or Azure (AKS), and agnostic of application technology framework.
  • Updated Oct 24, 2020
  • Shell

Improve this page

Add a description, image, and links to the infrastructure-automation topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the infrastructure-automation topic, visit your repo's landing page and select "manage topics."

Learn more