v0.8.0

Updating workflows @Benbentwo (#32)

Test

`WIP` Testing workflows @Benbentwo (#31)

📚️ Documentation

Partial Definition Implementation @Benbentwo (#29)

Please note this is an experimental feature

what

• Defaults to partial definition support

why

• Testing featuresets

references

• cloudposse/github-action-run-ecspresso#15
• cloudposse/github-action-deploy-ecspresso#22

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

v0.6.0

Test migrations @goruha (#10)

## what * Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?) * Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123

v0.5.0

Change BG color @goruha (#9)

## what * Change BG color to `cyan`

Update alpine Docker tag to v3.18 @renovate (#8)

This PR contains the following updates:

Package	Type	Update	Change
alpine	final	minor	3.17 -> 3.18

---

v0.4.0

Update README.md @goruha (#7)

## what * Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?) * Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a GitHub issue #123

v0.3.0

Demo 1 @goruha (#6)

## what * Set background color `blue`

v0.2.0

Demo 2 @goruha (#5)

## what * Set background color `green`

v0.1.0

Update alpine Docker tag to v3.17 @renovate (#2)

This PR contains the following updates:

Package	Type	Update	Change
alpine	final	minor	3.11 -> 3.17

---

Configure Renovate @renovate (#1)

Welcome to [Renovate](https://togithub.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/deploy-production.yaml (github-actions)
• .github/workflows/feature-branch.yml (github-actions)
• .github/workflows/hotfix-branch.yml (github-actions)
• .github/workflows/main-branch.yaml (github-actions)
• .github/workflows/release.yaml (github-actions)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update alpine Docker tag to v3.17

• Schedule: ["at any time"]
• Branch name: renovate/alpine-3.x
• Merge into: master
• Upgrade alpine to 3.17

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate. View repository job log here.