📝 Register a new app

[ymao2]

Brief summary of what this Epic is

Background

After finishing app-migration, we need to start to think about how to handle the request of registering a new app.

The key points we need to consider

• how to capture such request? : e.g. github issue or through cpanel
• steps for creating required infrastructure (namespace, ecr ..) on CP, auth0 and getting the app ready in cpanel which allow users to manage the app through cpanel
  • cluster related
    • namespace
    • resources: etc.
    • rbac
  • AWS app role + trust-relationships between AWS app role and CP role
  • Auth0 clients if auth is required
  • github workflows
  • Register the app in Cpanel
• how about static page app?

Current status for getting a app deployed

if something is missed, feel free to add them

• a few scripts + github workflow(?) for getting the infrastructure created on CP
• cpanel has the feature of registering an app which will get aws-role, auth-clients and github secrets & vars created
  There is no auto-step to link the above 2 steps. There is question about what is the best way to add the trust-relationship
• static page (?)

Done when

• A user-story and related flows has been well-defined
• A list of break-down tasks

List of issues in this epic

• ✡️ What is the user flow for registering an app to be deployed on CP? #1886
• ✨ Make Annotations and IngressClass configurable in the webapp-cp helm chart #1929
• 📚Comprehensive Documentation for Repository Creation and Environment Setup #2632
• 🔄 Update Control Panel Process for App Creation Post-Migration #2633
• 📦 Refactoring App Base Images for Public Hosting on GitHub Container Registry #2634
• 🛠️Documenting Self-Service of Cloud Platform Namespaces for App Owners #2635
• 📝 End-to-End Documentation for the New App Process #2636
• 📝 Update documentation about the supported Rshiny base images #2981
• ⭐ Onboard 2 New Apps #3300

[julialawrence]

Closing as duplicate of #1828