-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
resourcegroupstaggingapi_resources - new data source #17804
Conversation
website/docs/d/resourcegroupstaggingapi_resources.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/d/resourcegroupstaggingapi_resources.html.markdown
Outdated
Show resolved
Hide resolved
Add the |
Addressed the comments, thanks! |
Co-authored-by: Kit Ewbank <Kit_Ewbank@hotmail.com>
6d07399
to
6a61156
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looking really good, @DrFaust92 👍 Just going to switch from filter
to tag_filter
to match the API naming and re-verify everything.
website/docs/d/resourcegroupstaggingapi_resources.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/d/resourcegroupstaggingapi_resources.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/d/resourcegroupstaggingapi_resources.html.markdown
Outdated
Show resolved
Hide resolved
website/docs/d/resourcegroupstaggingapi_resources.html.markdown
Outdated
Show resolved
Hide resolved
Type: schema.TypeSet, | ||
Optional: true, | ||
Elem: &schema.Schema{Type: schema.TypeString}, | ||
ConflictsWith: []string{"filter"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ConflictsWith: []string{"filter"}, | |
ConflictsWith: []string{"tag_filter"}, |
} | ||
|
||
const testAccDataSourceAwsResourceGroupsTaggingAPIResourcesBasicConfig = ` | ||
data "aws_resourcegroupstaggingapi_resources" "test" {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Empty configuration is taking 30+ minutes to paginate in our testing accounts 😢 In this case, I think it is probably okay to omit the testing since the API doesn't provide any sort of "maximum results" parameter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i was afraid of this. i'm ok with omitting it. maybe hide it behind a flag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a similar issue with aws_ami
where unfiltered results would result in a huge result set as well. We skip including that testing with the hope that the unfiltered API operation would operate the same as a filtered one. Not aware of any particular issues with that in the last 3 years. We could put this behind an environment variable, but it is probably okay without it.
|
||
func testAccDataSourceAwsResourceGroupsTaggingAPIResourcesTagKeyFilterConfig(rName string) string { | ||
return fmt.Sprintf(` | ||
resource "aws_api_gateway_rest_api" "test" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API Gateway REST APIs can be slightly problematic:
- Throttled to 2 deletions/minute
- EDGE endpoints (default) are unavailable in GovCloud
Going to switch this to an easier resource such as a VPC to see if that cooperates a little better. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i tinkered a lot with this. was the simplest one i could think of at the time. i remember trying vpc but dont remember why i dropped it. IIRC it didn't propagate and results were empty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be having really good luck today as it seems to be passing with aws_vpc
resources and random tags. 😄
This has been released in version 3.38.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! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #17705
Output from acceptance testing: