Releases: deploymenttheory/go-api-http-client
v0.2.1
What's Changed
- updated docs for refactor changes by @ShocOne in #247
- Added Features: mandatory req delay, retry mechanism togglable by @thejoeker12 in #248
Full Changelog: v0.1.54...v0.2.1
v0.2.0
What's Changed
- Large Restructure of HTTP Client data flow.
- Migrated Jamf specific integration code to new repo (alongside other integrations) - github.com/deploymenttheory/go-api-http-client-integrations/jamf.
- Various small refactors, better error catching and easier to maintain logic.
- Code tidying, removal of comments.
- Flattening of package structure when not required elsewhere.
- Temporary removal of concurrency management until refactor can be implemented
Full Changelog: v0.1.53...v0.2.0
Upcoming
- Logging refactor
- Redirect refactor
- Concurrecy manager reimplementation
v0.1.53
v0.1.53
What's Changed
- Updated multipart comments and update func param names for clarity by @ShocOne in #220
- chore: experimenting with using a streaming technique rather than a b… by @ShocOne in #221
- chore: Refactor chunk size for file upload in multipart request to 2m… by @ShocOne in #222
- Dev multipartfix by @ShocOne in #223
- Refactor chunk size for file upload in multipart request to 10MB per … by @ShocOne in #224
- Dev multipartfix by @ShocOne in #225
- Refactor logUploadProgress function to include elapsed time in upload… by @ShocOne in #226
- chore: Improve logging and streaming for multipart file upload by @ShocOne in #227
- chore: Improve logging and streaming for multipart file upload by @ShocOne in #228
- chore: trial implemention of resumable uploads by @ShocOne in #229
- testing 64MB chunk size by @ShocOne in #230
- Refactor chunk size for file upload in multipart request to 64MB for … by @ShocOne in #231
- Refactor chunk size for file upload in multipart request to 8MB for i… by @ShocOne in #232
- Refactor addFilePart function to include custom headers for each part… by @ShocOne in #233
- Dev multipartfix by @ShocOne in #234
Full Changelog: v0.1.52...v0.1.53
v0.1.52
v0.1.51
v0.1.51
What's Changed
- Refactor createMultipartRequestBody to support custom content types a… by @ShocOne in #204
- Added support for multi file uploads following OAS3 spec by @ShocOne in #205
- V0.1.50 dev by @ShocOne in #206
- V0.1.50 dev by @ShocOne in #207
- Refactor multipart request handling and logging by @ShocOne in #208
- chore: Refactor addFilePart to use base64 encoding for file content by @ShocOne in #209
- Refactor addFilePart to use base64 encoding for file content by @ShocOne in #210
- V0.1.50 dev by @ShocOne in #211
- Refactor multipart request handling and logging by @ShocOne in #212
- increased ctx timeout by @ShocOne in #213
- removed context for testing and troubleshooting by @ShocOne in #214
- chore: troubleshooting context by @ShocOne in #215
- Refactor multipart request handling and logging by @ShocOne in #217
- Refactor multipart request handling and logging by @ShocOne in #218
Full Changelog: v0.1.50...v0.1.51
v0.1.50
v0.1.50
Full Changelog: v0.1.49...v0.1.50
v0.1.42
v0.1.41
v0.1.41
What's Changed
- Bump golang.org/x/net from 0.24.0 to 0.25.0 by @dependabot in #191
- Bump github/super-linter from 5.0.0 to 6 by @dependabot in #189
- chore: Refactor token acquisition and refresh logic in TokenManager by @ShocOne in #199
Full Changelog: v0.1.39...v0.1.41
v0.1.39
v0.1.39
Token Buffer Period Adjustment
Issue: The token lifetime was shorter than the buffer period set for token refresh, causing the client to never consider the token valid and to enter a loop of continuous token refresh attempts.
Solution: Implemented a maximum consecutive token refresh attempt limit. If this limit is exceeded, an error is thrown with a message indicating that the token lifetime is likely too short compared to the configured buffer period.
Details:
Added a check in the CheckAndRefreshAuthToken method to count consecutive refresh attempts and throw an error after a specified limit.
Enhanced the error message to clearly indicate the mismatch between the access token lifetime and the buffer period configured for token refresh.
- Support for String-Based Duration in JSON Config
Issue: JSON configuration did not support string-based duration values, causing unmarshalling errors when durations were specified as strings.
Solution: Added support for parsing duration strings in JSON configuration files.
Details:
Created a custom type JSONDuration to handle durations specified as strings in JSON.
Implemented UnmarshalJSON and MarshalJSON methods for JSONDuration to parse and format duration strings.
Updated the TimeoutConfig struct to use JSONDuration instead of time.Duration.
Modified the client configuration loading logic to handle the new JSONDuration type.
Ensured all instances where durations are used (e.g., token refresh buffer period, total retry duration, custom timeout) are updated to use JSONDuration and its methods.
What's Changed
- Cookies fixed hopefully by @thejoeker12 in #192
- fix by @thejoeker12 in #193
- Bug fix: by @ShocOne in #198
Full Changelog: v0.1.38...v0.1.39