chore: Remove dependency of AWS.Lambda.Powertools.Common on all Utilities
Why is this needed?
Utilities have a dependency on the AWS.Lambda.Powertools.Common project.
When the utility is compiled and packaged into a nuget package the AWS.Lambda.Powertools.Common is a dependency.
This behaviour is causing Diamond dependency issues in the project.
To address this we should copy the required files to each utility and make them completely isolated. This allows the client to not have to worry about dependencies between utilities and AWS.Lambda.Powertools.Common.
There is no need to delete the AWS.Lambda.Powertools.Common project but link the files in other projects, this will make it more readable in the solution explorer and makes maintenance easier because it's all in a single project.
Summary
chore: Remove dependency of AWS.Lambda.Powertools.Common on all Utilities
Why is this needed?
Utilities have a dependency on the AWS.Lambda.Powertools.Common project. When the utility is compiled and packaged into a nuget package the AWS.Lambda.Powertools.Common is a dependency. This behaviour is causing Diamond dependency issues in the project. To address this we should copy the required files to each utility and make them completely isolated. This allows the client to not have to worry about dependencies between utilities and AWS.Lambda.Powertools.Common. There is no need to delete the AWS.Lambda.Powertools.Common project but link the files in other projects, this will make it more readable in the solution explorer and makes maintenance easier because it's all in a single project.
Which area does this relate to?
Governance, Tracing, Logging, Metrics, Parameters, Idempotency
Solution
No response
Acknowledgment