v0.16.1

0.16.1 (Aug 12, 2024)

ENHANCEMENT

• restful_operation - Hornor Content-Type header when constructing the request body (76ab171)

BUG FIX

• Provider: Fix the incorrect handling of security.http.token.scheme (620c2fe)
• Fix issue in resource validation on path builder (b021ba9)

v0.16.0

0.16.0 (Aug 12, 2024)

BREAKING CHANGES

• Rework path builder to support more functions. The body pattern (i.e. body or body.x) now can add a chain of functions (applied from left to right), in form of $f1.f2(body.x). Removed the #(...) pattern in favor of url_path function. (#107)

• Moving the retry(_xxx) blocks from restful_resource and restful_operation to the provider retry block, with schema changes, as the previous resource level retry implementation is error-prone. (#112)

BUG FIXES

• Fix resource body validation error when referencing a dynamic output from other resource (#113)
• Fix the provider schema security.token.scheme (620c2fe)

v0.15.0

0.15.0 (Jul 22, 2024)

ENHANCEMENTS

• restful_operation - Support id_builder for building resource id (#104)

v0.14.1

0.14.1 (Jun 21, 2024)

BUG FIXES

• restful_operation - Supports output to be null (#100)

v0.14.0

0.14.0 (May 22, 2024)

BREAKING CHANGES

• restful_resource - Change the type of body, output from string to dynamic (#87)
• restful_resource - Read invoked from Create/Update now won't update the body (but still update the output). This makes those round trip inconsistent APIs won't cause error during the terraform apply, which makes the resource as tainted. Instead it will show the diff in the next terraform plan, which brings a chance for users to add the write_only_attrs/ignore_changes (#87)
• restful_operation - Change the type of body, delete_body, output from string to dynamic (#87)
• restful_resource data source - Change the type of output from string to dynamic (#87)

To migrate from versions earlier than v0.14.0, users expect to do the followings:

1. If the body (or alike) is constructed by jsonencode function, then remove the jsonencode call
2. If any reference of the output (or alike) is using jsondecode function, then remove the jsondecode call
3. Do a terraform apply (even though no diff is detected), that terraform will migrate the state file for you

v0.13.3

0.13.3 (May 21, 2024)

ENHANCEMENTS

• provider - Enable client API log (85f31b6)

BUF FIXES

• restful_resource - [read|update_delete]_path builder pattern supports $(body) (#96, 0c98b21)

v0.13.2

0.13.2 (May 16, 2024)

BUF FIXES

• Internal - Fix HeaderLocator always return true (b2d73fd )

v0.13.1

0.13.1 (May 16, 2024)

BUF FIXES

• restful_resource - (read_)selector handle selected part is removed out-of-band (#94 )

v0.13.0

0.13.0 (May 13, 2024)

ENHANCEMENTS

• Provider: mTLS support (#82)
• restful_resource - create_method supports PATCH (#86)
• restful_resource - body supports being an array (#90)

v0.12.0

0.12.0 (Dec 4, 2023)

BREAKING CHANGES

• restful_resource & restful_operation - Remove query for poll_xxx block. During polling, the actual query used is either from the polling url_locator (as the polling URL is expected to contain the complete URL, including the query needed), or inherit from the originating request if url_locator not specified. (#73)
• restful_resource - Update import_spec to remove some unnecessary properties, and allow body to be optional (#71)

ENHANCEMENTS

• restful_resource data source: Support precheck (#65)
• restful_resource data source: Supports method for GET, HEAD and (read-only) POST (#67)
• restful_resource resource & data source: Extend the output_attrs to support arrays (#70)
• restful_resouce (res&ds) & restful_operation: Support retry(_(create|read|update|delete)) (#75)
• restful_operation - Support delete_(method|body|path), (precheck|poll|retry)_delete and output_attrs (#79)

BUG FIXES

• Fix resty client TLS client config setting error: current transport is not an *http.Transport instance (#72)
• precheck|poll expose API error if the status_locator is not code, instead of returning the error indicating the status locating from header/response failed (#78)