Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

Basic validation and/or show more details about the provided pull-secret #17

Open
gbraad opened this issue Jan 15, 2022 · 0 comments
Open

Comments

@gbraad
Copy link
Collaborator

gbraad commented Jan 15, 2022

To prevent issues with the pull-secret, the component could perform basic validation.

When the pull secret has been pasted, it is checked for JSON-wellformedness. If not, the outer edge can turn red, and a callback can be given/variable set isValid = false;

It could even be possible to read basic data from the pull-secret. As the pull-secret takes the form of:

{
  "auths": {
    "cloud.openshift.com": {
      "auth": "b3B...Q==",
      "email": "gbraad@redhat.com"
    },
    "quay.io": {
      "auth": "b3B...Q==",
      "email": "gbraad@redhat.com"
    },
    "registry.connect.redhat.com": {
      "auth": "NTA...w==",
      "email": "gbraad@redhat.com"
    },
    "registry.redhat.io": {
      "auth": "NTA...w==",
      "email": "gbraad@redhat.com"
    }
  }
}

we could show:

Provided pull-secret belongs to:
Email:   g***d@r***t.com

Note: this could additionally state that the 'validness' (not expired) will be checked by the cluster.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant