Mateusz Gozdek
Mateusz Gozdek
Hmm, I guess this is likely because of multiple `replace` statements in `go.mod` file we have, which are not respected by `go get` or `go install`.
Err, we have https://github.com/kinvolk/lokomotive/blob/master/docs/concepts/flatcar-container-linux.md#customization. Isn't it sufficient?
>I totally missed that. But we can improve that create a how to guide by taking a use case. Please change the issue title to reflect that then :)
/remove-lifecycle rotten
/remove-lifecycle stale
/remove-lifecycle stale
/remove-lifecycle stale
Hmm, to be honest, my main motivation is only following Go best practices, which recommends avoid global variables. Also, I would like to understand the reasoning behind chosing: ```go var...
>Then they are not the same. The () at the end of the first block makes a big difference. In it, a variable with type http.FileSystem is initialized and assigned...
I was thinking about how the user interface for that could look like. What about: ``` resource "tls_x509_certificate_revocation_list" "clients" { certificates = tls_locally_signed_cert.client.*.public_cert_pem } output "crl" { value = tls_x509_certificate_revocation_list.clients.crl_pem...