Base64 encode response body
Closes: #157 Closes: #147 Closes: #145 Closes: #99 Closes: #72 Closes: #67 Closes: #38 Closes: #13 Closes: #11
Any chance we can get this PR merged and released? I am running into the same issue.
I maintain a terraform provider for Xen Orchestra and leveraging this new functionality would allow me to avoid reimplementing similar logic in the terraform provider.
What's the remaining work here? Is there any way I can help this effort?
@bendbennett @detro Also asking about the state of this PR. Any chance to have this merged?
Can we merge this?
Hi all :wave:, sorry about the delayed response.
This PR is currently on-hold as there is a need to skip certain test scenarios for specific terraform versions ( 0.14.* ) and the testing framework currently does not have that capability. There has been some internal discussion about design of that testing functionality but our team's attention is currently elsewhere at the moment.
Is this feature available in some sort of a fork? because i really need this
Hi @kishaningithub 👋,
As mentioned above there are some additional considerations so this PR is currently on-hold until we've addressed the issue of being able to skip certain test scenarios for specific terraform versions. Apologies for any inconvenience.
Thanks for the hard works folks, what's the release schedule so we can get this out? 🙏
Hi there @darren-recentive 👋🏻 !
The team has released this feature with 3.4.0 yesterday: https://registry.terraform.io/providers/hashicorp/http/latest/docs/data-sources/http#response_body_base64
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.