fix: top level comment not replacing existing ones

[juniarz]

Fixes the issue where top level comments are not replaced after an update to the function.

Description of changes

This fixes the issue where the regex for the function top level comments are not working, resulting in duplicates of the Amplify params that is generated after an update to a function (especially resources).

Issue #, if available

NA

Description of how you validated changes

Updated a function in my local environment and the top level comments are correctly replaced.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jhockett]

Hi @juniarz, thanks for your contribution!

It looks like a unit test in packages/amplify-category-function/src/__tests__/provider-utils/awscloudformation/service-walkthroughs/execPermissionsWalkthrough.test.ts is failing because the snapshot is out of date. You can run yarn jest --updateSnapshot <path to test> to update it automatically.

Additionally, are you able to add a test case to ensure the comment is updated correctly?

[juniarz]

Hi @juniarz, thanks for your contribution!

It looks like a unit test in packages/amplify-category-function/src/__tests__/provider-utils/awscloudformation/service-walkthroughs/execPermissionsWalkthrough.test.ts is failing because the snapshot is out of date. You can run yarn jest --updateSnapshot <path to test> to update it automatically.

Additionally, are you able to add a test case to ensure the comment is updated correctly?

Hey, I resolved the issue, please check it out!