feat(pci-instances): add list of ssh keys

[Tsiorifamonjena]

Description

Ticket Reference: #TAPC-4623, #TAPC-4626

Additional Information

[lolottetheclash]

I think you should improve the SSH key regex: it should not valid the fact that it can contain some blank spaces into the ssh key, and also you should trim it before testing it

[aTurmo]

You can merge those two use effect (same dependencies)

[lolottetheclash]

@Tsiorifamonjena I was thinking that ssh key should not contain any blank space but I think it's wrong, it can contain between each part. To trim it is a good practise, but maybe check the right ssh regex as it's already present in the manager :)

[Tsiorifamonjena]

@Tsiorifamonjena I was thinking that ssh key should not contain any blank space but I think it's wrong, it can contain between each part. To trim it is a good practise, but maybe check the right ssh regex as it's already present in the manager :)

You were right @lolottetheclash :)

here is the ssh key format <type> <base64-encoded-key> and base64-encoded-key should not contain any blank space. I searched the entire manager but there is no regex. Validation is done on the backend side for existing form.

I improve the regex and I let you see

[lolottetheclash]

When I click on "create a new ssh key" for the first time, I have the impression that page reloads, do you have the same behavior?

[Tsiorifamonjena]

When I click on "create a new ssh key" for the first time, I have the impression that page reloads, do you have the same behavior?

@lolottetheclash the translation was probably loaded in my local, that's why I didn't have the same behavior.
The problem was from common translation not yet load on mounting the AddSshKey component for the first time (after click create a new ssh key) then react-i18next fetch and there is a fallback.

I fix it by adding the namespace in the init I let you see