Ben Drucker

I don't think so. Is there a reason you're not using a proper relative path, i.e. `./foo`? This is important to distinguish between registry/builtin packages and local modules.

Hey I have a bit of a backlog of open source stuff at the moment. Wasn't planning on adding this but I'd be happy to help w/ pull requests.

This would involve changing the URL for Stripe.js and adding the method to https://github.com/bendrucker/stripe-errback. Can't make any promise as to when/if I'll do this myself but I will happily devote...

Are you interested in finishing this?

Hmm, I don't think so. You could submit PRs to the upstream modules to allow true lazy loading upon call instead of eagerly loading. Happy to review those if you...

Cool, I'll at least leave this open until we have an official comment from Stripe on this behavior. I think it's highly undesirable to work around this on a wrapper...

CLI compatibility isn't the issue here. It's a question of the Go packages and their public (exported) API. Those are explicitly not part of the Terraform compatibility promise. _Legal speculation...

Retitled as there's no direct relationship to `required_version`. There are many rules that could potentially emit an issue about a lack of some required configuration, in which case there would...

> The simplest workaround for now is to always emit a range that includes the module path in a rule like terraform_required_version. Yep, thought about this. It's an improvement for...

To implement the behavior where `-chdir` is handled differently than sub-command flags, Terraform manually processes (and strips) it before passing off the args to be parsed as flags: https://github.com/hashicorp/terraform/blob/a9230c9e7582c353c224cf0f4832d472ce042c0d/main.go#L428