create new skill for AWS labmda hosted not working as expected

[kokhanchyk]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request 
[ ] Other... Please describe: 

Expected Behavior

when create ask new -p profile_name alexa skill and java AWS lambda should create in one account, not in separate.

Current Behavior

CLI Snapshot
If applicable, add screenshots to help explain your problem.

Steps to Reproduce (for bugs)

1. create default profile with ask configure for account A

2. create new profile called "test" with ask configure -p for account B

3. create new alexa skill with ask new (for account A),
   programming languade: java,
   host your skill's backend resources: AWS Lambda,
   template: hello world,
   skill name: test skill A,
   folder name: test_skill_a

4. test skill A successfully created in Alexa console of account A,
   and lambda successfully created and deployed in AWS account A.

5. create new alexa skill with ask new -p test (for account B),
   programming languade: java,
   host your skill's backend resources: AWS Lambda,
   template: hello world,
   skill name: test skill B,
   folder name: test_skill_b

6. test skill B successfully created in in Alexa console account A,
   and lambda successfully created and deployed in account B.

this is the bug, when I create ask new -p test alexa skill created in one account but lambda deployed to the other account.

Possible Solution

Your Environment and Context

• ask-cli version: 2.22.4
• Operating System and version: Ubuntu 20.04
• Node.js version used for development: v12.18.4
• NPM version used for development: v12.18.4

[CamdenFoucht]

Hi @kokhanchyk thank you so much for the bug report. We will try to reproduce it and put out a fix for this issue.