feat(cloudfront): find and replace text in the code of CloudFront Functions during synth

[SydneyUni-Jim]

Issue # (if applicable)

Closes #30492

Reason for this change

Primarily to allow deploying a CloudFront Function and its Key/Value Store in the same stack, without having to deploy the Key/Value Store first, manually retrieve its ID, and then hardcode the ID into the Function's code.

Secondarily to allow other values in a CloudFront Function's code to be changed when deploying into different environments, dev verses prod for example.

Description of changes

• aws_cloudfront/README.md
  • Update the CloudFront Functions and Key Value Store sections.
• aws_cloudfront/function.ts
  • Add struct FunctionCodeFindReplace.
  • Add struct FunctionCodeOptions, with the optional findReplace property.
  • Change struct FileCodeOptions to extend FunctionCodeOptions.
  • Add struct InlineCodeOptions, which extends FunctionCodeOptions with no additional properties.
    • For symmetry with FileCodeOptions and as a future extension point.
  • Add an optional options parameter to FunctionCode.fromInline.
  • Add private method FunctionCode.findReplace.
  • Change InlineCode.render to call FunctionCode.findReplace.
  • Change FileCode.render to call FunctionCode.findReplace.

Backwards compatible API changes

• FunctionCode.fromInline gains a second optional parameter.
• FileCodeOptions gains an optional findReplace property.

Description of how you validated changes

• Add describe('find/replace in function code'… to function.test.ts.
• Add integ.function-find-replace.ts
  • Deploys a CloudFront distribution, function, and key-value store.
  • Use find/replace to get the ID of the key-value store into the function.
  • Exercises the function to test the function can access the key-value store.

Checklist

• 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

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[SydneyUni-Jim]

In the last PR Linter / validate-pr, node core dumped from a bus error. The prior validate-pr had succeeded.

[4/4] Building fresh packages...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error /home/runner/work/aws-cdk/aws-cdk/node_modules/@lerna/create/node_modules/nx, /home/runner/work/aws-cdk/aws-cdk/node_modules/@nx/devkit/node_modules/nx, /home/runner/work/aws-cdk/aws-cdk/node_modules/lerna/node_modules/nx: Command failed.
Exit code: 135
Command: node ./bin/post-install
Arguments: 
Directory: /home/runner/work/aws-cdk/aws-cdk/node_modules/@nx/devkit/node_modules/nx
Output:
Bus error (core dumped)
Error: Process completed with exit code 135.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 66c0d03
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository