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

[Docs]: Incorrect limit for LF-Tags #37608

Closed
Udbv opened this issue May 20, 2024 · 4 comments · Fixed by #37638
Closed

[Docs]: Incorrect limit for LF-Tags #37608

Udbv opened this issue May 20, 2024 · 4 comments · Fixed by #37638
Labels
documentation Introduces or discusses updates to documentation. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/lakeformation Issues and PRs that pertain to the lakeformation service.
Milestone

Comments

@Udbv
Copy link
Contributor

Udbv commented May 20, 2024

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lakeformation_lf_tag

Description

Resource docs:
The maximum number of values permitted is 15.

From AWS docs:

The following limits are soft limits:

  • The maximum number of LF-Tags that can be created is 1000.

  • The maximum number of values that can be defined for a LF-Tag is 1000.

I've checked: 999 tag values

resource "aws_lakeformation_lf_tag" "product" {
key = "product"
values = [for i in range(1,1000): i]
}
image

References

https://docs.aws.amazon.com/lake-formation/latest/dg/lf-tag-considerations.html

Would you like to implement a fix?

Yes

@Udbv Udbv added the documentation Introduces or discusses updates to documentation. label May 20, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/lakeformation Issues and PRs that pertain to the lakeformation service. label May 20, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label May 20, 2024
@justinretzolk justinretzolk added good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels May 20, 2024
Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.51.0 milestone May 23, 2024
Copy link

This functionality has been released in v5.51.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!

Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/lakeformation Issues and PRs that pertain to the lakeformation service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants