Image speaks for itself.
Pretty fresh session, no special prompt. No /goal no do at all costs etc
Ok everything seems to work as of now
Next steps would be to adapt the proepr sox fix
So for the pangolin machine we correctly use the named ssh key, lets have the same for the engineer.
I gues we would need to adapt the boot strap for that
Next would be to adapt the keys that can encrypt/edit/decrypt secrets
As stated we want the the pub we clairfyied to be able to interact with the sops file
and after that we would need to incorporate the pangolin secrets (pangolin.yaml) into the bigger secrets.yaml. (I will manually check if we have the secret value already declared in the bitwarden folder)
Image speaks for itself.
Pretty fresh session, no special prompt. No /goal no do at all costs etc