Deployment workflow #109
Merged
Deployment workflow #109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robertandremitchell
approved these changes
Nov 4, 2024
DanPaseltiner
approved these changes
Nov 4, 2024
There was a problem hiding this comment.
This looks good to me @shanice-skylight thanks for your work here. This workflow appears to only be able to be triggered manually, do we have plans to take this one step further and automatically trigger a deployment every time we merge to main and build a new image of the app? Starting with a manual process is totally reasonable to me.
|
Yes, once we confirm the workflow acts as expected. I'll change it to automatically trigger when a PR is merged to main. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PULL REQUEST
Summary
This PR will add a workflow that is triggers the workflow named target_workflow in the repo named phdi-playground. See explanation of each step of the workflow below:
Users are prompted to provide two inputs:
-target_service: The service name (e.g., phdi-playground) that identifies the target repository where the workflow should be triggered.
-target_version: The version (e.g., v1.0.0) that will be passed to the target workflow.
Related Issue
Fixes Issue 79
Additional Information
Checklist