aws-amplify / aws-amplify/amplify-hosting
Post Deploy Phase!
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
One thing that is very much missing from amplify is a "post deploy" phase in which one can write scripts or perform operations after the full CI CD process succeeds.
e.g. run a script which creates a github release for the just deployed release.
**Describe the solution you'd like**
Add a post deployment phase to make amplify more customizable
Contributor guide
Research direction
The issue names no files, tests, or entry points. Begin by mapping the full CI/CD workflow and existing customization options, then define when a post-deploy operation runs and how it is configured. Done means a script can run after a successful full deployment, including the GitHub release example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100