feat(cloudwatch-dashboards): add support for queryLanguage property
Issue # (if applicable)
Closes #34482
Reason for this change
CloudWatch recently added support for using multiple query languages to query logs. Currently, CDK is missing the functionality to specify a query language when creating a Log Query Widget inside a CloudWatch Dashboard.
Description of changes
Applied suggested implementation by @ykethan and added tests.
Describe any new or updated permissions being added
N/A
Description of how you validated changes
Added unit test and updated integ test.
Checklist
- [x] My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Clarification Request: is there any way to view logs to debug the build failure?
Clarification Request: is there any way to view logs to debug the build failure?
The build logs are posted in the comment from aws-cdk-automation here
@kumsmrit thank you for the guidance. The build failure was due to invalid code references I added in the README updates. I have fixed it, and the build is passing now.
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).
AWS CodeBuild CI Report
- CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
- Commit ID: 7348aaaf77767756823d769473e55f60a71b2f3e
- Result: SUCCEEDED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.