First draft of GitHub Radius feature spec#154
First draft of GitHub Radius feature spec#154zachcasper wants to merge 3 commits intoradius-project:mainfrom
Conversation
Signed-off-by: Zach Casper <zachcasper@microsoft.com>
Signed-off-by: Zach Casper <zachcasper@microsoft.com>
| 1. As an open-source developer, I want to deploy an application stored in a public GitHub repository to my cloud environment. I expect GitHub Radius to build and deploy the application: | ||
| 1. Using AWS | ||
| 1. Using Azure | ||
|
|
There was a problem hiding this comment.
are we intentionally leaving out local K8s?
There was a problem hiding this comment.
Yes. Since Radius is running in GitHub it must have a publicly accessible API end point. This eliminates local and on-premises Kubernetes clusters.
|
|
||
| 1. A CloudFormation stack is opened. The user reviews the stack then clicks Create stack. | ||
|
|
||
|  |
There was a problem hiding this comment.
idea: how about keeping templates in OCI registry? we will get out of box: versioning, immutable releases, mature well-known technology.
|
|
||
| ### Step 3: Creating an AWS environment | ||
|
|
||
| 1. The user clicks Deploy and sees options for creating AWS, Azure, or Google Cloud environments. The user clicks **Create AWS environment**. |
There was a problem hiding this comment.
Are Github environments meant to be a replacement for Radius environments
There was a problem hiding this comment.
The spec is saying that Github environments are where environment definitions are mastered.
| - AWS Region | ||
| - AWS IAM Role ARN | ||
| - A workflow is dispatched which performs an AWS login test and confirms the adequate IAM permissions are available | ||
|
|
There was a problem hiding this comment.
This would be backed by radius environments and credentials too, when the ephemeral radius comes up correct?
There was a problem hiding this comment.
No, this would be a standalone workflow separate from Radius.
6 participants
This pull request adds a comprehensive feature specification document for the GitHub Radius prototype. The document outlines how Radius will be integrated into GitHub repositories and Copilot, detailing user journeys, technical flow, and UI mock-ups for deploying applications to AWS and Azure via GitHub. It serves as a foundational reference for the prototype's scope, user experience, and technical requirements.
Key additions in this specification:
Feature Overview and Scope:
User Experience and Journeys:
Technical and Security Details: