Cypress tests for federated scenarios
From #17914, it became evident that we need to be doing end-to-end testing of LoginCluster and Peer federated scenarios.
The first thing that we can test is the login procedure, but indeed we'll be writing other test cases when wb2 gets more federation aware.
Things to take into consideration for this story:
arvboxuses seem not to issue salted tokens (or the satellite cluster isn't passing some required param like
remote=clustedId?). The current Cypress test cluster uses
Login.PAM; it would be convenient to double-check it behaves correctly.
- Running multiple federated clusters will require improvements on the cluster launch script. If the bash script gets too complicated, maybe we can make a go program similar to
integration_test.go. Selecting random ports reliably and building the config file with the
RemoteClustersentries pointing to the correct
host:portwould be one of the requirements.
We can replicate what we have on the dev clusters:
zzzza(LoginCluster, equivalent to
zzzzb(Satellite of zzzza, equivalent to
zzzzc(Peered with zzzza and zzzzb, equivalent to
Current cypress test could just keep being run against