You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(custom-resources): use loggingFormat instead of deprecated logFormat (#35015)
Use loggingFormat instead of deprecated logFormat in the Provider class
### Issue # (if applicable)
Closes#35002
### Reason for this change
The `logFormat` property in Lambda Function is deprecated and will be removed in the next major release. This change updates the Provider class to use the recommended `loggingFormat` property instead, eliminating deprecation warnings.
### Description of changes
- Updated the Provider class in `provider.ts` to use `loggingFormat` instead of the deprecated `logFormat` property
- Added a test in `provider.test.ts` to verify that no deprecation warnings are emitted when creating a Provider
- Ensured backward compatibility by maintaining the same functionality
This change is minimal and focused on replacing the deprecated property with its recommended alternative. The functionality remains the same, but the code now follows best practices and avoids deprecation warnings.
### Describe any new or updated permissions being added
No new or updated IAM permissions are needed for this change.
### Description of how you validated changes
- Added a unit test that verifies no deprecation warnings are emitted when using the Provider class
- Manually verified that the Provider class still functions correctly with the new property
- Ensured backward compatibility by testing with existing code
### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
0 commit comments