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]: While ingestigating Issue/33383 i noticed the system_log_level documentation doesnt match available provider options #38789

Closed
aidenvaines-bjss opened this issue Aug 9, 2024 · 4 comments
Labels
documentation Introduces or discusses updates to documentation.

Comments

@aidenvaines-bjss
Copy link

Documentation Link

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

Description

While ingestigating Issue/33383 i noticed the system_log_level documentation doesn't match available provider options.

The documentation states

system_log_level - (optional) for JSON structured logs, choose the detail level of the Lambda platform event logs sent to CloudWatch, such as ERROR, DEBUG, or INFO.

At apply time you will see this error when setting logging_config{system_log_level) to "ERROR"

Error: expected system_log_level to be one of ["DEBUG" "INFO" "WARN"], got ERROR

References

No response

Would you like to implement a fix?

Yes

@aidenvaines-bjss aidenvaines-bjss added the documentation Introduces or discusses updates to documentation. label Aug 9, 2024
Copy link

github-actions bot commented Aug 9, 2024

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.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 9, 2024
@network-charles
Copy link
Contributor

The issue may be in the implementation of the resource. According to the official AWS documentation the Terraform documentation is correct.

@aidenvaines-bjss aidenvaines-bjss closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 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.

@terraform-aws-provider terraform-aws-provider bot removed the needs-triage Waiting for first response or review from a maintainer. label Aug 12, 2024
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 Sep 12, 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.
Projects
None yet
Development

No branches or pull requests

2 participants