Currently, the Component creation dialog involves the creation of SPITokenBinding. We propose migrating to RemoteSecret. This transition will involve updating the Component creation dialog to create RemoteSecrets instead of SPITokenBindings.

Here is an example of how the RemoteSecret might be structured:

apiVersion: appstudio.redhat.com/v1beta1
kind: RemoteSecret
metadata:
    name: github-com-token
    namespace: myns
    annotations:
        appstudio.redhat.com/sp.repository: "redhat-appstudio/remote-secret"
    labels:
        appstudio.redhat.com/sp.host: github.com
        ui.appstudio.redhat.com/secret-for: Build
 spec:
    targets:
    - namespace: myns
      secret:
        name: appstudio-token-47ce801b-a8b5-4104-8810-22239c3f4057
        type: kubernetes.io/basic-auth 

 
SecretData Upload Options: To upload the SecretData, you can choose between two approaches:

1. Secrets Approach: You can follow the interactive method outlined in the documentation (https://github.com/redhat-appstudio/remote-secret/blob/main/docs/USER.md#delivering-the-secrets-interactively).

1. Update in Place: Alternatively, you can update the SecretData in place for more secure and interactive handling (https://github.com/redhat-appstudio/remote-secret/blob/main/docs/USER.md#providing-remotesecret-data-in-a-more-secure-and-interactive-way).

OAuth Flow Initiation: To initiate the OAuth flow, you can use the annotation appstudio.redhat.com/sp.oauthurl