A GitHub Action to get a list of affected atmos stacks for a pull request
GitHub Action for Triggering Affected Spacelift Stacks
This is GitHub Action that can be used as a workflow for automatic updates via Pull Requests in your infrastructure repository according to versions in components sources.
GitHub Action to retreive a setting from [atmos](https://github.com/cloudposse/atmos) configuration.
This Github Action is used to run Terraform apply for a single, Atmos-supported component with a saved planfile in S3 and DynamoDB.
This Github Action is used to detect drift
This Github Action is used to remediate drift
This Github Action is used to run Terraform plan for a single, Atmos-supported component and save the given planfile to S3 and DynamoDB.
GitHub Action that outputs list of Atmos components by jq query
Github Action Auto-Format runs several repository "hygiene" tasks for repositories: - The `readme` target will rebuild `README.md` from `README.yaml`. - The `github_format` target adds all of Cloud Posse's standard repository housekeeping files (including GitHub Actions workflows) to the repository's `.github` folder. - The `terraform_format` target ensures consistent formatting across all Terraform files in the repository.
This is an opinionated composite Github Action that implements a workflow based on the popular `release-drafter` action to automatically draft releases with release notes that are derived from PR descriptions as they are merged into the default branch. ``` Under default settings, `auto-release` will also cut a new release from the default branch after every merge into it. However, releases are not cut for merges of pull requests with a `no-release` label attached. In that case, the release notes are left as a draft and a release with all unreleased changes will be made the next time a pull request without the `no-release` label is merged into the default branch.
Converts AWS region names from full names to abbreviations
Template repository of composite GitHub Action
Github Action CD Argo CD...
Github Action CI Docker will build, test, and deploy a container image using [Docker](https://www.docker.com/). The [`example`](https://github.com/cloudposse/github-action-ci-docker/.github/workflows/docker.yml/) showcases how to use private and public ECR repositories for storage. If desired, it will also trigger a deployment on another repository.
Create Datadog Notify Event
Deploy on Kubernetes with ArgoCD
Deploy on ECS with [Escpresso](https://github.com/kayac/ecspresso)
Deploy on Kubernetes with HelmFile
Opinionated way to deploy Docker image app with Spacelift
Build Docker image and push it
Up docker compose and run tests in specific container
Check if docker image exists by pulling it
Promote docker image
Get Environments settings from private settings action provider
This repository wraps the environment information action, allowing it to be used as a replacement in support of various string functions and namespace standardization.
GitHub Action that automatically generates or updates `v<major-release>` tags every time a new release is published.
[Workaround implementation](https://github.com/community/community/discussions/17245#discussioncomment-3814009) - Read matrix jobs outputs
[Workaround implementation](https://github.com/community/community/discussions/17245#discussioncomment-3814009) - Write matrix jobs outputs
Template repository of composite GitHub Action
Monorepo random controller used for demo
Action to manage to deploy and purge preview environments depends on PR labels
Remove labels used to control deployments with [github-action-preview-environment-controller](https://github.com/cloudposse/github-action-preview-environment-controller)
GitHub Action for Managing Release Branches
This GitHub Action validates that the major label is only assigned to Pull Requests targeting the default branch, enhancing the management of significant changes.
Run ECS task with [Escpresso](https://github.com/kayac/ecspresso)
This GitHub Action implement [workaround](https://nitratine.net/blog/post/how-to-pass-secrets-between-runners-in-github-actions/) for the problem [`Combining job outputs with masking leads to empty output`](https://github.com/actions/runner/issues/1498). The problem was described in [`GitHub Action documentation`](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idoutputs) - `Outputs containing secrets are redacted on the runner and not sent to GitHub Actions`.
Get GitHub deployment object by ref and environment name
Install atmos for use in GitHub Actions
Trigger Spacelist stack synchronously
GitHub Action to sync two docker repositories.
This is a Github Action that will automatically update the `context.tf` file in the calling repo against the most recent version published by Cloud Posse. If a new version is detected, a Pull Request will be opened to update it. If the repo version is found to be out of date, a pull request is opened to update it.
A GitHub Action to securely store Terraform plan files in an S3 bucket with metadata storage in DynamoDB.
A GitHub Action to run Terratest tests and post the results as a build artifact.
Template repo for GitHub Actions written in TypeScript
This is a Github Action to validate the `CODEOWNERS` file by running a series of checks against the `CODEOWNERS` file to ensure that it's valid and well-linted. Ensuring your repository's `CODEOWNERS` file is valid can be critical to the development process if, for instance, your project uses [branch protection](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) conditions that rely on definitions in `CODEOWNERS`.
Wait for commit status
Define YAML document, filter it with JSON query and get result as outputs