chore: Replace Makefile with atmos.yaml (#73)

Author: osterman

Makefile

@@ -1,4 +1,3 @@
----
 #
 # This is the canonical configuration for the `README.md`
 # Run `make readme` to rebuild the `README.md`
@@ -17,13 +16,17 @@ license: "APACHE2"
 github_repo: cloudposse/github-action-atmos-terraform-apply
 
 badges:
-  - name: "Latest Release"
-    image: "https://img.shields.io/github/release/cloudposse/github-action-atmos-terraform-apply.svg"
-    url: "https://github.com/cloudposse/github-action-atmos-terraform-apply/releases/latest"
-  - name: "Slack Community"
-    image: "https://slack.cloudposse.com/badge.svg"
-    url: "https://slack.cloudposse.com"
-
+  - name: Latest Release
+    image: https://img.shields.io/github/release/cloudposse/github-action-atmos-terraform-apply.svg?style=for-the-badge
+    url: https://github.com/cloudposse/github-action-atmos-terraform-apply/releases/latest
+  - name: Last Updated
+    image: https://img.shields.io/github/last-commit/cloudposse/github-action-atmos-terraform-apply.svg?style=for-the-badge
+    url: https://github.com/cloudposse/github-action-atmos-terraform-apply/commits
+  - name: Slack Community
+    image: https://slack.cloudposse.com/for-the-badge.svg
+    url: https://cloudposse.com/slack
+
+# List any related terraform modules that this module may be used with or that this module depends on.
 related: []
 
 description: This Github Action is used to run Terraform apply for a single, Atmos-supported component with a saved planfile in S3 and DynamoDB.
@@ -68,15 +71,15 @@ usage: |-
   > If you are using `atmos < 1.63.0` please use `v1` version of this action.
 
   The action expects the atmos configuration file `atmos.yaml` to be present in the repository.
-  
+
   The action supports AWS and Azure to store Terraform plan files. 
   You can read more about plan storage in the [cloudposse/github-action-terraform-plan-storage](https://github.com/cloudposse/github-action-terraform-plan-storage?tab=readme-ov-file#aws-default) documentation. 
   Depends of cloud provider the following fields should be set in the `atmos.yaml`:
-  
+
   #### AWS
-  
+
   The config should have the following structure:
-  
+
   ```yaml
   integrations:
     github:
@@ -99,9 +102,9 @@ usage: |-
   ```
 
   #### Azure
-  
+
   The config should have the following structure:
-  
+
   ```yaml
   integrations:
     github:
@@ -150,27 +153,27 @@ usage: |-
   ```    
 
   ### Support OpenTofu
-  
+
   This action supports [OpenTofu](https://opentofu.org/).
-  
+
   > [!IMPORTANT]
   > **Please note!** OpenTofu supported by Atmos `>= 1.73.0`.
   > For details [read](https://atmos.tools/core-concepts/projects/configuration/opentofu/)
-  
+
   To enable OpenTofu add the following settings to `atmos.yaml`
     * Set the `opentofu-version` in the `atmos.yaml` to the desired version
     * Set `components.terraform.command` to `tofu`
-  
+
   #### Example
-  
+
   ```yaml
-  
+
   components:
     terraform:
       command: tofu
-  
+
   ...
-  
+
   integrations:
     github:
       gitops:
@@ -181,7 +184,7 @@ usage: |-
   ### Workflow example
 
   In this example, the action is triggered when certain events occur, such as a manual workflow dispatch or the opening, synchronization, or reopening of a pull request, specifically on the main branch. It specifies specific permissions related to assuming roles in AWS. Within the "apply" job, the "component" and "stack" are hardcoded (`foobar` and `plat-ue2-sandbox`). In practice, these are usually derived from another action. 
-  
+
   > [!TIP] 
   We recommend combining this action with the [`affected-stacks`](https://atmos.tools/integrations/github-actions/affected-stacks) GitHub Action inside a matrix to plan all affected stacks in parallel.
 
@@ -213,14 +216,14 @@ usage: |-
               atmos-config-path: ./rootfs/usr/local/etc/atmos/
   ```
   ### Migrating from `v3` to `v4`
-  
+
   The notable changes in `v4` are:
 
   - `v4` works only with `atmos >= 1.158.0`
   - `v4` supports atnos `templates` and `functions`
 
   ### Migrating from `v2` to `v3`
-  
+
   The notable changes in `v3` are:
 
   - `v3` works only with `atmos >= 1.99.0`
@@ -231,23 +234,23 @@ usage: |-
   The only required migration step is updating atmos version to `>= 1.99.0`   
 
   ### Migrating from `v1` to `v2`
-  
+
   The notable changes in `v2` are:
-  
+
   - `v2` works only with `atmos >= 1.63.0`
   - `v2` drops `install-terraform` input because terraform is not required for affected stacks call
   - `v2` drops `atmos-gitops-config-path` input and the `./.github/config/atmos-gitops.yaml` config file. Now you have to use GitHub Actions environment variables to specify the location of the `atmos.yaml`.
-  
+
   The following configuration fields now moved to GitHub action inputs with the same names
-  
+
   |         name            |
   |-------------------------|
   | `atmos-version`         |
   | `atmos-config-path`     |
-  
-  
+
+
   The following configuration fields moved to the `atmos.yaml` configuration file.
-  
+
   |              name        |    YAML path in `atmos.yaml`                    |
   |--------------------------|-------------------------------------------------|
   | `aws-region`             | `integrations.github.gitops.artifact-storage.region`     | 
@@ -260,14 +263,14 @@ usage: |-
   | `enable-infracost`       |  `integrations.github.gitops.infracost-enabled` |
   | `sort-by`                |  `integrations.github.gitops.matrix.sort-by`    |
   | `group-by`               |  `integrations.github.gitops.matrix.group-by`   |
-  
-  
+
+
   For example, to migrate from `v1` to `v2`, you should have something similar to the following in your `atmos.yaml`:
-  
+
   `./.github/config/atmos.yaml`
   ```yaml
   # ... your existing configuration
-  
+
   integrations:
     github:
       gitops:
@@ -285,7 +288,7 @@ usage: |-
           sort-by: .stack_slug
           group-by: .stack_slug | split("-") | [.[0], .[2]] | join("-")
   ```
-  
+
   `.github/workflows/main.yaml`
   ```yaml
     - name: Plan Atmos Component
@@ -296,11 +299,11 @@ usage: |-
         atmos-config-path: ./rootfs/usr/local/etc/atmos/
         atmos-version: 1.63.0
   ``` 
-  
+
   This corresponds to the `v1` configuration (deprecated) below.
-  
+
   The `v1` configuration file `./.github/config/atmos-gitops.yaml` looked like this:
-  
+
   ```yaml
   atmos-version: 1.45.3
   atmos-config-path: ./rootfs/usr/local/etc/atmos/
@@ -315,9 +318,9 @@ usage: |-
   sort-by: .stack_slug
   group-by: .stack_slug | split("-") | [.[0], .[2]] | join("-")  
   ```
-  
+
   And the `v1` GitHub Action Workflow looked like this.
-  
+
   `.github/workflows/main.yaml`
   ```yaml
     - name: Plan Atmos Component
@@ -327,9 +330,9 @@ usage: |-
         stack: "plat-ue2-sandbox"
         atmos-gitops-config-path: ./.github/config/atmos-gitops.yaml
   ```
-  
+
   ### Migrating from `v0` to `v1`
-  
+
   1. `v1` drops the `component-path` variable and instead fetches if directly from the [`atmos.yaml` file](https://atmos.tools/cli/configuration/) automatically. Simply remove the `component-path` argument from your invocations of the `cloudposse/github-action-atmos-terraform-apply` action.
   2. `v1` moves most of the `inputs` to the Atmos GitOps config path `./.github/config/atmos-gitops.yaml`. Simply create this file, transfer your settings to it, then remove the corresponding arguments from your invocations of the `cloudposse/github-action-atmos-terraform-apply` action.
 
@@ -345,10 +348,10 @@ usage: |-
   | `terraform-version`      |
   | `aws-region`             |
   | `enable-infracost`       |
-  
-  
+
+
   If you want the same behavior in `v1` as in `v0` you should create config `./.github/config/atmos-gitops.yaml` with the same variables as in `v0` inputs.
-  
+
   ```yaml
   - name: Terraform apply
     uses: cloudposse/github-action-atmos-terraform-apply@v1
@@ -357,9 +360,9 @@ usage: |-
       component: "foobar"
       stack: "plat-ue2-sandbox"
   ```
-  
+
   Which would produce the same behavior as in `v0`, doing this:
-  
+
   ```yaml
   - name: Terraform apply
     uses: cloudposse/github-action-atmos-terraform-apply@v0
@@ -374,8 +377,5 @@ usage: |-
       aws-region: "us-east-2"
   ```
 
-include:
-  - "docs/github-action.md"
-
-# Contributors to this project
-contributors:
+include: []
+contributors: []

README.yaml

@@ -0,0 +1,12 @@
+# Atmos Configuration — powered by https://atmos.tools
+#
+# This configuration enables centralized, DRY, and consistent project scaffolding using Atmos.
+#
+# Included features:
+# - Organizational custom commands: https://atmos.tools/core-concepts/custom-commands
+# - Automated README generation: https://atmos.tools/cli/commands/docs/generate
+#
+
+# Import shared configuration used by all modules
+import:
+  - https://raw.githubusercontent.com/cloudposse/.github/refs/heads/main/.github/atmos/terraform-module.yaml