StephenWithPH

>[...] that endpoint fails when the Content-Type header can't be parsed as a multipart header, which may mean that whatever gsutil is sending isn't recognized by fake-gcs-server. I'm having a...

This seems to cross over with https://github.com/terraform-providers/terraform-provider-vault/issues/122. Linking here so searchers can find the two issues.

Adding on additional information to the sentiment that the ignore_changes workaround is insufficient. Thanks to https://github.com/hashicorp/terraform/pull/30517, Terraform now slaps the user's hand for ignoring a computed attribute (`branches` in this...

Adding commentary in case it helps anyone... I set the deprecated [policies](https://www.terraform.io/docs/providers/vault/r/gcp_auth_backend_role.html#policies) field rather than the recommended [token_policies](https://www.terraform.io/docs/providers/vault/r/gcp_auth_backend_role.html#token_policies) field, and that resolved a gnarly issue I was having (by way...

I landed here after following the thread from #1955. Although https://docs.flutter.dev/development/tools/sdk/releases still doesn't display checksums, the data is there in the json response from the server: ![Screen Shot 2022-07-21 at...

I agree that this would be a nice thing to have. Having said that, I was able to work around this by making two changes. First, specify the route prefix...

I was unable to solve this problem with NerdFonts (having installed them). ``` spacebar -m config icon_font "Hack Nerd Font:Regular:12.0" ``` I still had a rendered question mark in the...

> I am **truly sorry** for neglecting a project I love for so long, and I will write a full apology on the mailing lists along with the release announcement....

https://github.com/orgs/community/discussions/25238#discussioncomment-3247035 shows a simplified example that works.

https://github.com/hashicorp/terraform/releases/tag/v1.2.0 includes https://github.com/hashicorp/terraform/pull/30486. This **may** suppress the `etag` warnings we see. Has anyone on this issue upgraded to v1.2.0 yet and seen same/different behavior regarding `etag`?