Thanks to visit codestin.com
Credit goes to github.com

Skip to content

bug: when recreating the infrastructure components it doesn't change as expected #12150

Open
@ljsomm

Description

@ljsomm

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Whenever I try to change any infrastructure component on localstack, cdklocal neither update it nor recreate it with the expected attributes.

Example case:

I created an SQS called queue, after change its name to queue1 it used the cdk unique ID to name the queue as following:

arn:aws:cloudformation:sa-east-1:000000000000:stack/PersonalProjectsStack/24c51b91

Also tested this in default cdk in my AWS environment and it gracefully changed the name (prolly recreating the queue, but however it was done, it was the expected goal).

Expected Behavior

Update the SQS queue correctly without needing to recreate the container or destroy and redeploying everything.

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

localstack:
container_name: aws_local_ts
image: localstack/localstack
environment:
- DEBUG=1
ports:
- 4566:4566
- 4566-4620:4566-4620

Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

aws sqs --profile local list-queues

Environment

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    aws:sqsAmazon Simple Queue Servicestatus: backlogTriaged but not yet being worked onstatus: staleTo be closed soon due to stalenesstype: bugBug report

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions