Remove legacy node-fetch and document mod/cloudfront ☁️

[RobAndrewHurst]

Description

I have removed the node-fetch reference in the cloudfront.js mod.

I also added in documentation for the script.

GitHub Issue

#1641

Type of Change

Please delete options that are not relevant, and select all options that apply.

• ✅ Bug fix (non-breaking change which fixes an issue)
• ✅ Documentation

Code Quality Checklist

• ✅ My code follows the guidelines of XYZ
• ✅ My code has been commented
• ✅ Documentation has been updated
• ✅ New and existing unit tests pass locally with my changes
• ✅ Main has been merged into this PR

[dbauszus-glx]

I have updated the docs. There was some heavy nesting on the properties which were defined as params.

This is now cleaned up.

I also added the module requires to the module block.

[dbauszus-glx]

I still want to test this failing. I think the try...fetch is just there to throw an error if the key is undefined or fails to sign. I want to actually test this providing a false key and a false resource.

[dbauszus-glx]

#1542 must be merged into this PR.

The provider module must return an Error rather than text failed to retrieve resource.

The cloudfront module must export null if the cloudfront key is not defined rather than throwing an Error which isn't caught.

The cloudfront module must return an Error and not just throw and Error with no return if the resource is not available or failed to resource.

The urlSigner should be a signer module to be imported by the provider module for internal use. signedUrl request should be rerouted to the cloudfront signer module.

[dbauszus-glx]

This is good to go. I create a seperate issue for the code structure and security concerns.

#1651

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud