v0.7.0

Workflow Demo: April 2024 @milldr (#30)

## what - Change the example app color

why

• Demo workflows

references

• n/a

Allow Environment Info from another Org @Benbentwo (#27)

## what

• allow input org for environment info

why

• GHE and might need to read environment info from another org. this supports that

Fix Environment Config @milldr (#26)

## what - Point back to `main`

why

• Previous PR pointed to a branch to debug but didn't revert after that branch was merged (and deleted)

references

• https://github.com/cloudposse/example-app-on-ecs/actions/runs/8104291954/job/22150657936

feat: Github Checks and Release Drafter @milldr (#25)

## what - Added all our typically GitHub checks and PR template - Fixed token for release drafter - Removed redundant `concurrency` and `permissions` settings

why

• QoL improvements for Pull Requests
• We dont need a special token to draft a release. Plus if we do create a PAT, it should only have read access to the private config
• concurrency needs only to be set once and should be set at the top level. Where the workflow is started
• permissions needs only to be set once and should be set where the permissions are required. Any reusable workflow should define what permission that workflow needs

references

• customer engagement

New Workflow `Rollback` @Benbentwo (#23)

## what * Rolls back environments defined in `.github/workflows/rollback.yaml` to a supplied tag.

why

• Environments might need to be rolled back if a critical bug is found

Update README.yaml @Benbentwo (#15)

## what * Update readme.yaml

Feature: `hotfix` workflows @Benbentwo (#22)

## what * Adds hotfix workflows

why

• Provides a way to patch a specific release and reintegrate the changes

Feature: Consolidated Workflows @Benbentwo (#12)

## what * All workflows are local * Adds config for environment usage (see [.github/configs/environment.yaml](.github/configs/environment.yaml)

why

• Easier to understand

references

• related: cloudposse-examples/app-on-eks-with-argocd#13

📚️ Documentation

update description @Benbentwo (#28)

## what

• update description
• update readme

why

• clarifies the purpose of so many workflows