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

aws_cur_report_definition doesn't support Parquet #8765

Closed
waffleshop opened this issue May 24, 2019 · 5 comments
Closed

aws_cur_report_definition doesn't support Parquet #8765

waffleshop opened this issue May 24, 2019 · 5 comments
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Milestone

Comments

@waffleshop
Copy link

waffleshop commented May 24, 2019

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 "me too" comments, 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

Terraform Version

0.12.0

Affected Resource(s)

  • aws_cur_report_definition

Terraform Configuration Files

provider "aws" {
  profile     = "default"
  region      = "us-east-1"
  version     = "2.12.0"
}

resource "aws_cur_report_definition" "cost_report" {
  report_name                = "mycostreport"
  time_unit                  = "HOURLY"
  format                     = "Parquet"
  compression                = "Parquet"
  additional_schema_elements = ["RESOURCES"]
  s3_bucket                  = "mybucketname"
  s3_prefix                  = "hourly-costs"
  s3_region                  = "us-east-1"
  additional_artifacts       = ["ATHENA"]
}

Debug Output

Panic Output

Expected Behavior

Resource should have been created. This AWS API supports these values according to their documentation. Additionally, this AWS resource can be created using the Python boto3 package.

Actual Behavior

terraform plan throws the following errors:

Error: expected format to be one of [textORcsv], got Parquet
...
Error: expected compression to be one of [GZIP ZIP], got Parquet
...
Error: expected additional_artifacts.0 to be one of [QUICKSIGHT REDSHIFT], got ATHENA
...

Steps to Reproduce

  1. terraform apply

Important Factoids

References

@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/costandusagereportservice labels May 25, 2019
@zioalex
Copy link

zioalex commented Mar 13, 2020

Can we have also add support for ATHENA is this issue or would be better to have a new on?.

@robbruce
Copy link
Contributor

@zioalex see #12428

@bflad bflad self-assigned this Sep 2, 2020
@bflad bflad added this to the v3.5.0 milestone Sep 2, 2020
@bflad
Copy link
Contributor

bflad commented Sep 2, 2020

Support for this functionality has been merged and will release with version 3.5.0 of the Terraform AWS Provider, likely tomorrow. Thanks to @robbruce for the implementation. 👍

@bflad bflad closed this as completed Sep 2, 2020
@ghost
Copy link

ghost commented Sep 3, 2020

This has been released in version 3.5.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 for triage. Thanks!

@ghost
Copy link

ghost commented Oct 3, 2020

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.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Oct 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants