v1.0.8

What's Changed

• Feat/update secrets on expected response by @arielsepton in #79

Full Changelog: release-1.0.7...release-1.0.8

v1.0.7

What's Changed

• fix: use new secretInjectionConfigs keyMappings field in resource docs by @Chewie in #74
• Add Support for Additional HTTP Methods in Method Field by @arielsepton in #77

New Contributors

• @Chewie made their first contribution in #74

Full Changelog: release-1.0.6...release-1.0.7

v1.0.6

What's Changed

• feat: improve observation validation for POST requests by @arielsepton in #69
• feat: add customizable removal check for Request resource by @arielsepton in #71
• feat: support labels and annotations for secrets by @arielsepton in #72
• bump version to v1.0.6 by @arielsepton in #73

Full Changelog: release-1.0.5...release-1.0.6

v1.0.5

What's Changed

• feat: implement custom state check by @arielsepton in #61
• feat: implement flexible http method mapping by @arielsepton in #62
• feat: Add support for authentication credentials in ProviderConfig by @arielsepton in #63

Full Changelog: release-1.0.4...release-1.0.5

v1.0.4

What's Changed

• feat(environment-proxy): allow to use proxy settings from the environment by @barunavo in #38
• feat: implement owner reference for secrets by @arielsepton in #43

New Contributors

• @barunavo made their first contribution in #38

Full Changelog: release-1.0.3...release-1.0.4

v1.0.3

What's Changed by @arielsepton

• Enhanced Nested JSON Handling: The Contains function now correctly handles nested JSON structures, ensuring more accurate state comparisons for resources with complex JSON data.
• Added test cases for the Contains function, including tests for various nested JSON structures. Verified that the modified function performs as expected with these test cases.
  Tests include scenarios for nested JSON structures, exact matches, partial matches, and mismatches.

Impact

Enhanced State Management: This release significantly improves the provider's ability to maintain the desired state by accurately tracking changes in resources with nested JSON structures.

v1.0.2

This release introduces several enhancements to the DisposableRequest resource, allowing for more efficient handling of reconciliation intervals and looping behavior.

Changes made

• Added shouldLoopInfinitely and nextReconcile fields to the DisposableRequest resource.
  • shouldLoopInfinitely: Allows the reconciliation loop to run indefinitely. If set to true, the controller will continue to reconcile the resource without stopping.
  • nextReconcile: Specifies the duration after which the next reconcile should occur, providing more control over reconciliation intervals.

These changes allow for efficient handling of JWT token refresh scenarios by leveraging the shouldLoopInfinitely and nextReconcile fields.

For a detailed example, refer to the updated composition in the examples folder.

v1.0.1

What's Changed

• Ensured that the provider behaves gracefully in the absence of a PUT mapping, avoiding crashes and improving overall stability. by @arielsepton in #23
• Bump version to v1.0.1 by @arielsepton in #24

Full Changelog: v1.0.0...v1.0.1

v1.0.0

This release introduces a significant enhancement to Crossplane's provider-http, enabling the secure injection of sensitive data from Kubernetes secrets both into HTTP requests and from HTTP responses into Kubernetes secrets.

Changes Made

• API Version Update: The API version has been bumped from v1alpha1 to v1alpha2 to incorporate the new feature.
• Secret Injection Syntax: Users can now utilize the syntax {{ name:namespace:key }} to inject secret data into request bodies and headers.
• Response Data Patching: Implemented the capability to patch response data from HTTP requests into Kubernetes secrets, allowing dynamic updates.
• Example Updates: Provided updated examples (DisposableRequest and Request) to illustrate the utilization of secret injections and response data patching.

v0.2.0

Breaking Changes

Updated the DisposableRequest API to correct a typo, changing all occurrences of "desposible" to "disposable".

No migration needed; simply delete the previous instance as it has no state.