This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 136
rules are not hermetic at all #80
Comments
See: #21 We don't include it because they are essentially useless without authentication configured and Bazel's current guidance on credentials is fundamentally non-hermetic.
|
Okay, if I send a PR that at least documents what it commands it requires? |
Absolutely :) |
ensonic
added a commit
to ensonic/rules_k8s
that referenced
this issue
Dec 1, 2017
This is useful to know for setting up a hermetic build environment. See bazelbuild#80
ensonic
added a commit
to ensonic/rules_k8s
that referenced
this issue
Dec 5, 2017
This is useful to know for setting up a hermetic build environment. See bazelbuild#80
ensonic
added a commit
to ensonic/rules_k8s
that referenced
this issue
Dec 13, 2017
This is useful to know for setting up a hermetic build environment. See bazelbuild#80
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The 'run' commands for create/apply/delete shell out to kubectl and gcloud. This should maybe be mentioned at least in a README. Ideally the rules will pull the commands through the WORKSPACE for hermeticity, right?
For background when running them through dazel, one will need to installed them to the dazel docker container.
The text was updated successfully, but these errors were encountered: