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

Missing resource awscc_timestream_influx_db_instance #1953

Closed
ewbankkit opened this issue Aug 14, 2024 · 0 comments · Fixed by #1954
Closed

Missing resource awscc_timestream_influx_db_instance #1953

ewbankkit opened this issue Aug 14, 2024 · 0 comments · Fixed by #1954
Assignees
Labels

Comments

@ewbankkit
Copy link
Contributor

ewbankkit commented Aug 14, 2024

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
  • The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.

The AWS::Timestream::InfluxDBInstance schema was available on or before 04/25/2024 (#1623) but no awscc_timestream_influx_db_instance is generated.

It seem like this was a transposition error from internal/provider/generators/allschemas/available_schemas.2024-04-25.hcl to internal/provider/all_schemas.hcl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant