[BUG] No easy way to change (or remove) pull-secret

[gbraad]

When the pull-secret is stored in secure storage, it is difficult to change this to another one. This can happen when the pull-secret is revoked or has to be changed. However when the pull-secret API is used to store a copy&pasted pull-secret, it is not possible to use crc config to reset or unset it. Only crc cleanup allows for the removal, but this command has too many side-effects.

[gbraad]

A possible solution would be to use crc config set/unset pull-secret as an abstracted (intercepted) config option to deal with the pull secret API.

however, when crc config view is used, only ******** is shown to indicate a value has been given.

[anjannath]

Should we instead document how the user can remove it by using the os provided tools (keychain in macos and credential manager on windows)? my concern is having both pull-secret and pull-secret-file as config options would be confusing.

[ben-alkov]

Should we ... document how the user can remove it by using the os provided tools...?

Yes, please, including Linux.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.