Releases: carwow/terraform-provider-hirefire
Releases · carwow/terraform-provider-hirefire
v0.7.0
What's Changed
- Add upscale_on_initial_job to Manager resource @stevenharman in #35
- Add checkup_frequency to Application resource @stevenharman in #36
- Update golang to v1.22 (and security related dependency updates)
New Contributors
- @stevenharman made their first contribution in #35
Full Changelog: v0.6.0...v0.7.0
v0.7.0-pre
What's Changed
- Add upscale_on_initial_job to Manager resource @stevenharman in #35
- Add checkup_frequency to Application resource @stevenharman in #36
- Update golang to v1.22 (and security related dependency updates)
New Contributors
- @stevenharman made their first contribution in #35
Full Changelog: v0.6.0...v0.7.0-pre
v0.6.0
v0.5.2
v0.5.1
Bump go v1.18, update CircleCI images
v0.5.0
Add Manager::Worker::HireFire::JobLatency
v0.4.1
Manager resource and null (zero) values (#19) * Manager resource and null (zero) values Hirefire API changed how it handles null values in the manager resource, specifically: - notify* - *scale_timeout - *scale_limit Also, logdrain in the application resource now requires a specific format. Plus, updated readme to explain how to run terrafrom with a local build. * Run terraform with a dev version of the provider
v0.4.0
Force new manager resource when changing type The API started misbehaving when changing type and setting properties from the previous type to null. The API client is very simple and always sends all of the possible properties for all manager types. Forcing the creation of a new manager when changing the type avoids these edge cases and inconsistencies, keeping the API client simple.
v0.3.5-noop
Hirefire API is not behaving correctly. In order to keep carwow's terraform working, I am making all resources read operation a noop.