Description of the problem / feature request:

An equivalent of --incompatible_strict_action_env that affects repository_ctx.execute.

Feature requests: what underlying problem are you trying to solve with this feature?

When I write repository rule implementations I often forget to declare the environment variables they depend on, so they are not reevaluated when those change, leading to incorrect builds, and requiring users to call bazel clean --expunge when the environment changes.

I have tried to filter the environment down to what I need before passing it to repository_ctx.execute, but the full environment is always added anyway:

A way to enforce the environment to be strict would be very helpful to avoid these kind of bugs in repository rules.

Have you found anything relevant by searching the web?

#7026