You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
We can NOT check for the existence of the pull-secret, as this requires the daemon.
The pull-secret is 'optional' to be provided during the onboarding.
The actual check will happen when the daemon is available.
Yeah, I am fine with the daemon as single point of truth (or state :)) , just point out the case, as this is a technical constraint but from an UX perspective is a bit strange (at least).
Annoyance rather than a blocker. The field is optional (does not prevent the user from progressing).
And the onboarding is a single-time event, unless the user 'resets'.
Parking on backlog
gbraad
changed the title
Pull secret always asked during on boarding process
[Annoyance] Pull secret always asked during on boarding process
Jan 28, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Testing an upgrade scenario where:
crc cleanup
(as I want to keep pull secret on the keyring)After install crc version, the onboarding process asks me for the pull secret (the pull secret is already stored at the keyring)
The text was updated successfully, but these errors were encountered: