Releases: cloudposse-archives/terraform-aws-eks-spotinst-ocean-nodepool
Releases · cloudposse-archives/terraform-aws-eks-spotinst-ocean-nodepool
v0.4.3
🚀 Enhancements
Add several outputs @applike-ss (#15)
what
- Added several outputs to make the created resources usable from outside the module
why
- A user may want to be able to create launch specs based on the created ocean
- A user may want to be able to use the workers role/instance profile arn/name
- A user may want to be able to re-use the used ami for the ocean in another launchspec to keep instances amis in sync
v0.4.2
🚀 Enhancements
Chore: run `make github/init` @korenyoni (#14)
what
- Run
make github/init
why
- Update
context.tf
to latest release of null-label, to support all null-label features. - If
context.tf
is incompatible between the parent module and the child module, Terraform will error out. - Running
make github/init
updates GitHub Actions workflows and related assets to their latest distributions from build-harness. - Update
null-label
module instantiation used for instance profile.
references
v0.4.1
🐛 Bug Fixes
Fix support of enabled flag, update provider requirements @Nuru (#13)
what
- Fix support of
enabled
flag - Update
spotinst
provider requirement to 1.56
why
- All Cloud Posse modules should work and not create resources when
enabled = false
and required variables are provided. This module failed. - PR #10 requires
spotinst
provider >= 1.56; earlier versions do not support theinstance_metadata_options
block.
v0.4.0
v0.3.0
Support HTTP tokens for IMDSv2 @max-lobur (#10)
what
- Similar to terraform-aws-ec2-instance this should support http_* options for the metadata
_required
flag does not actually follow best practices but this is to match the existing ec2 module (see above)http_endpoint
is not present in the provider so I did not add it.
why
- We want to enforce mandatory IMDSv2 HTTP tokens control for Spotinst pool similar to regular pools.
references
v0.2.0
Allow using `kubernetes` provider V1 @aknysh (#9)
what
- Allow using
kubernetes
provider V1 - Bump module versions
- Update GitHub actions
why
kubernetes
provider V2 has issues with race conditions when creating/updating/deleting EKS clusters- Allow top-level modules to decide on which version of the
kubernetes
provider to use - Keep up to date
v0.1.1
v0.1.0
v0.0.4
v0.0.3
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.22.1 @renovate (#6)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | terraform | patch | 0.22.0 -> 0.22.1 |
Release Notes
cloudposse/terraform-null-label
v0.22.1
Add var.attributes to end of context.attributes, not vice versa @Nuru (#114)
#### what - Add `var.attributes` to end of `context.attributes`, not vice versa - Update to current workflows (with some exceptions) #### why - Modules should append to attributes passed in, not insert themselves ahead of others - New features, like auto-format (but holding back some, because this is a special module) #### references - closes #113 - closes #108Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR has been generated by WhiteSource Renovate. View repository job log here.