Skip to content
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

Feature Request: Allow data source aws_ec2_spot_price to return empty results #17446

Open
cageyv opened this issue Feb 3, 2021 · 2 comments
Open
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.

Comments

@cageyv
Copy link
Contributor

cageyv commented Feb 3, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Some Availability Zones do not have a spot price for some reason
The API says there are no prices available
"Error: no EC2 Spot Price History found matching criteria; try different search"
The AWS Managed Console shows a similar picture
If we send a request without specifying AZ and there is no price in at least one AZ, the same error will occur.
The AWS documentation says this parameter is optional. Probably a bug in the terraform provider.

New or Affected Resource(s)

  • aws_ec2_spot_price

Potential Terraform Configuration

data "aws_ec2_spot_price" "this" {

  allow_empty_results  = true

  instance_type     = "t3.medium"
  availability_zone = "us-west-2a"

  filter {
    name   = "product-description"
    values = ["Linux/UNIX"]
  }
}

References

aws ec2 describe-spot-price-history

image
image

Relates:

@cageyv cageyv added the enhancement Requests to existing resources that expand the functionality or scope. label Feb 3, 2021
@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Feb 3, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Feb 3, 2021
@breathingdust breathingdust removed the needs-triage Waiting for first response or review from a maintainer. label Sep 4, 2021
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Dec 26, 2023
@cageyv
Copy link
Contributor Author

cageyv commented Dec 30, 2023

Still actual
But probably new AWSCC provider could solve it

@github-actions github-actions bot removed the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Dec 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

No branches or pull requests

2 participants