Taylor D. Edmiston

It appears to install fine via `pipenv` on Python 3.9.6 so I don't think Python 3.9 is the issue. Hmm.

Hmm good points. I'll give it a shot and see how it goes. Thanks for the quick reply.

This is a great suggestion. I tried obvious ways of searching like `#tag1`, `[tag1]`, etc for the multi-tag use case before ending up here. It would be nice to have...

Thank you for this good writeup. I experienced the same issue today as well with Terraform CLI v1.2.4 backed by Terraform Cloud... but using remote execution mode. I'm really surprised...

I'd really like to have this updated to the latest as well. Is there anything we can do to help from the dev side?

My use case is the same as OP. I came here to report the same issue after I couldn't figure out why cloning a private repo like `git clone [email protected]:myorg/myrepo.git`...

I also saw the [`HUB_PROTOCOL`](https://github.com/github/hub/blob/2d4b6cb6b980b9e70a9b11b385dc1331d5faf69f/share/man/man1/hub.1.ronn#L138) env var mentioned in issue https://github.com/github/hub/issues/1788. I gave that a shot but ran into the same issue: ``` $ export HUB_PROTOCOL=git $ hub clone myrepo/myorg...

Thanks - I don't think it's clear to me why we would need to hit the GitHub API to clone. Couldn't it simply be building the `git clone ...` command...

That makes sense. I do want to communicate with the GitHub API on operations that require it. I would strongly prefer not to grant access to that via my raw...

The problem is that IPs for e.g., Terraform Cloud, are dynamic. I do not think there is actually a whitelist one can use. I just get failed apply after failed...