-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_spot_fleet_request OnDemandTargetCapacity #7011
Comments
Hmm... might be related #4866 |
Is this ended up merged or it is still on review? Any other workarounds? It would be great if we could simply specify "On-Demand capacity" when we create spot fleet request. |
starting to work on this is dependent on #12732 |
#12732 is merged now; this feature would be very helpful. |
This functionality has been released in v3.46.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
This issue was originally opened by @deitch as hashicorp/terraform#19907. It was migrated here as a result of the provider split. The original body of the issue is below.
Current Terraform Version
Use-cases
AWS Spot Fleets support having a certain minimum number of target capacity as on-demand instances, to ensure a minimum threshold of always-available instances. See API here, CLI here, as well as this example
I might have missed it, but it doesn't appear in the parameters for aws_spot_fleet_request
Attempted Solutions
Proposal
References
Not much to add, unless I missed that it exists?
Thanks!
The text was updated successfully, but these errors were encountered: