wip: l2 images #42
wip: l2 images #42
Conversation
0x416e746f6e
force-pushed
the
trunk/l2
branch
from
e58ab4b to
447a823
Compare
0x416e746f6e
force-pushed
the
trunk/l2
branch
from
d26faee to
145218b
Compare
0x416e746f6e
force-pushed
the
trunk/l2
branch
from
0e37839 to
e85b24d
Compare
0x416e746f6e
force-pushed
the
trunk/l2
branch
7 times, most recently
from
1127cde to
dbaeecc
Compare
0x416e746f6e
force-pushed
the
trunk/l2
branch
from
dbaeecc to
427002a
Compare
| @@ -0,0 +1,14 @@ | |||
| rust: | |||
There was a problem hiding this comment.
When we just grab rust from debian backports this wont be necessary. I'll take care of it.
There was a problem hiding this comment.
we would still need a way to pin rust version somehow per image type (backports or not).
|
|
||
| BuildPackages=golang | ||
| libssl-dev | ||
| rustup |
There was a problem hiding this comment.
Switch to backports rust, I'll take care of this
There was a problem hiding this comment.
yes, just pls make it possible to use different versions of rust on different image kinds.
| # | ||
| # rendered by vault-agent/gomplate | ||
| # | ||
| [[- range ( ( gcp.Meta "attributes/ssh-keys" ) | strings.Split "\n" ) ]] |
There was a problem hiding this comment.
Isn't allowing ppl to SSH in a security risk?
There was a problem hiding this comment.
it is.
however this line makes sure that the keys are rendered only on the image built with dev profile. so, we are ok on prod images.
and on dev images, well we already allow anyone with console access in + use predefined root password. I don't think that (secret and non public) ssh keys added by vault-agent are making it any worse security-wise here.
(move snippets around to the right places)
0x416e746f6e
force-pushed
the
trunk/l2
branch
from
62da9c3 to
e7954c7
Compare
(cherry picked from commit ea20da4)
0x416e746f6e
force-pushed
the
trunk/l2
branch
from
ea20da4 to
cf2f4b2
Compare
5 participants
implement scripts for l2 workloads building