Add 3rd step for offline registration
Description
As discussed in team and confirmed the design with @kwwii, shift current step to into 3. Then move the following wording into step 2:
visit the SUSE Customer Center (SCC) offline registration tool https://scc.suse.com/register-offline/rancher.
/forwardport v2.13.0
@richard-cox sorry for asking but I completely miss what is the sense of a forwardport 🤔
By the time this v2.12.1 change can merge it will go into a release-2.12 branch and not master. The v2.13.0 issue ensures the change also goes into the go-forward branch
Then we have to do this for the whole epic
as long as there's issues in both v2.12.1 and v2.13.0 then whatever works, though normally we would have the main issues target the latest unreleased minor and create backports (i forward ported this one as i thought it was a one off).
The tests look good, but I think this should have an E2E manual check as it's a new feature.
If the other team does not have an E2E test, our branch will fail every time they change something. The client is not going to change because it has all unit tests. If the specification changes there, we should change them here too.
If you still prefer to have the feature covered, please feel free to do so.
Tested on Rancher v2.12.0-rc2 / Dashboard v2.12.0-rc2
- When the user clicks
Visit SCC, they are redirected to the SUSE Customer Center (SCC) login page. - If the user is already authenticated with SCC, they are taken directly to the Register Rancher Manager Offline page:
https://scc.suse.com/register-offline/rancher
https://github.com/user-attachments/assets/02af471f-fb85-493b-bb19-aad0551165e7