Paul Draper

I agree with this request. It's a pain now for Starlark to even read the `--stamp` value (#11164). --- > Returning a constant file wouldn't break rules that are already...

> For some reason this flag is barely documented `--define` is ["legacy"](https://bazel.build/docs/configurable-attributes). > it looks like --define does what you need. It seems this still requires cooperation from rule authors...

I don't see why it's a hard or bad idea to have a variable available even as early as the loading phase. --- Currently, my best workaround is to write...

> One more thing: if we have global variables that could theoretically be consumed anywhere (no consumes declare that they need it), it's hard to figure out what needs to...

I want to disable the lockfile because I don't use Terraform for provider resolution. I compile the provider, copy to the right location, and run Terraform. All this futzing around...

I don't understand why it was designed this way....there is a cache key. If users wanted their caches scoped by branch, or tag, or commit hash, they would include that...

>> I would like to be have a two-way connection between the ReactiveForms control and the native element > There is no "the element" or even "any element", necessarily. A...

Agreed, I recently switched to redocly-cli and it works beautifully.

snowflake_database_grant says it's deprecated and to use snowflake_grant_privledges_to_account_role snowflake_grant_privledges_to_account_role says to use a dedicated ownership resource type. And round and round it goes.

Environments variables are strings.