Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.
We've a deploy key in salt master, let's use it.
Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.
We've a deploy key in salt master, let's use it.
Roles core and saltmaster have been successfully fixed and applied.
$ salt windriver state.sls_id staging_private_repository roles/saltmaster/staging windriver: ---------- ID: staging_private_repository Function: file.directory Name: /opt/salt/private/staging Result: True Comment: Directory /opt/salt/private/staging updated Started: 01:42:15.402422 Duration: 5.32 ms Changes: ---------- /opt/salt/private/staging: New Dir ---------- ID: staging_private_repository Function: git.latest Name: ssh://vcs@devcentral.nasqueron.org:5022/source/private-staging.git Result: True Comment: ssh://vcs@devcentral.nasqueron.org:5022/source/private-staging.git cloned to /opt/salt/private/staging Started: 01:42:15.414312 Duration: 58070.73 ms Changes: ---------- new: ssh://vcs@devcentral.nasqueron.org:5022/source/private-staging.git => /opt/salt/private/staging revision: ---------- new: 3668bc40de3ee19269b4a54933bce73e7d86deb2 old: None
Ok, works fine now:
Still GID to do.
I need this task to solve T1572.
Some ideas to make this code more useful:
After a few dozens of seconds, I've got:
Fun, after systemctl enable --now snapd.socket I got the following message:
Restrict OS architecture for Starship
stderr:
error: snap "starship" is not available on stable for this architecture (armhf)
but exists on other architectures (amd64, i386).