aws-samples / aws-samples/amazon-connect-copy

Lambda Prefix A->B Mapping Not Working

Open
#48 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
40
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Hi,

When copying instance A to instance B and specifying the lambda_prefix_a and lambda_prefix_b arguments in connect_diff, the lambda ARN is not updated with the lambda_prefix_b when doing the copy over to instance B.

In the connect_copy script, I see the "sub_lex_bot()" function being invoked when copying over contact flows and contact flow modules for the Lex bot mappings, but I don't see a similar function being invoked when copying the contact flows and contact flow modules for Lambda function mappings. Am I missing something or is the lambda function ARN mapping logic missing?
![image](https://github.com/aws-samples/amazon-connect-copy/assets/136620868/43fb60e4-62aa-4933-8f1a-0010ae676d5a)

Here is a portion of the output of our connect_diff command:
![image](https://github.com/aws-samples/amazon-connect-copy/assets/136620868/e3f4fa49-ce9d-4836-bfe2-c7b932899e86)

Version used: 1.3.5

Contributor guide

Open the contributing guide

Research direction

Start in the connect_copy script and compare the existing sub_lex_bot() handling for Lex mappings with the Lambda mapping path used for contact flows and contact flow modules. Reproduce the copy with lambda_prefix_a and lambda_prefix_b, then verify that Lambda ARNs are updated to the destination prefix in the copied resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, shell
Domain
cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.