Releases: Mastercard/terraform-provider-restapi
Releases · Mastercard/terraform-provider-restapi
v1.9.0
v1.8.0
New
- Data sent to the API can be marked as sensitive by setting the
API_DATA_IS_SENSITIVE=true
environment variable thanks to @ipleten! - Dependencies are now vendored with
govendor
and scripting updated to support it - Per the previous note, we're now vendoring the latest Terraform (TF .12) to support the latest provider protocol. Thanks to @on4tux for the pointer in #30!
Fixed
- Contributors are great! The README gives some helpful pointers for getting started
v1.7.0
New
- Added cookie jar support thanks to @TMaYaD!
- Added support for dealing with xssi prefixes thanks to @TMaYaD!
- Added support for the
force_new
parameter (see README.md) thanks to @TMaYaD! - Added some test cases and CI scaffolding thanks to @burbon!
Fixed
- The test cases were fixed thanks to a patch from @burbon!
- We are
go fmt
, finally thanks to a patch from @TMaYaD!
Noteworthy
- The parameters for
api_client
have been modified from a long list to a typed structure of params.
v1.6.0
New
- Add
id_attribute
json list support, thanks @davidweterings!
Fix
- Improved debug logging for the datasource
v1.5.1
v1.5.0
v1.4.0
v1.3.0
New
- Add ability to set id_attribute per-resource and per-datasource as an override to provider config. Thanks @rberlind for the idea!
- Make id_attribute aware of how to find a value multiple levels deep in the results rather than as a top-level value only. Example: with the data
{ "attrs": { "id": 1234 }, "config": { "foo": "abc", "bar": "xyz"} }
, you can now get the id of1234
by settingid_attribute
toattrs/id
. Thanks @rberlind for the idea! - Added some handy internal functions to make working with complex data types safer and easier.
Fixes
- Do not fail with mysterious Go panics if type assertions fail during datasource lookup
v1.2.2
== Fixes
- Do not fail in the datasource if the API returns a non-string for the ID attribute (thanks for the report, @mlosapio)
- Fix datasource import regression introduced during the splitout of (get|put|post|delete)_path
- In rare cases, a failed internal creation for a critical resource during provider init may propagate as a success
== New
- Do not require
write_returns_object
orcreate_returns_object
on the provider if you're just using the datasource - Added terraform-specific test cases to exercise the code and avoid future regressions