Dominik Schubert

Hi @iulspop! As @jubis already mentioned using PRO seems to be a requirement for this to work. There might still be some minor issues, that I'd be willing to assist...

@iulspop Did you get a chance to try this yet?

Hi @lee-butn ! Unfortunately I cannot reproduce your issue. Please pull the latest images and try the steps below: ```yaml # docker-compose.yaml version: "3.8" services: localstack: container_name: "${LOCALSTACK_DOCKER_NAME-localstack_main}" image: localstack/localstack-pro...

Please start with `DEBUG=1` and check if you can see any errors in the localstack logs. Might be an issue with reconstructing the state from the persisted state file. :thinking:...

@bamajap @irgeek @redterror The reported bug should now be fixed and will be included in the tagged 1.4 release. You can also pull the latest image ` docker pull localstack/localstack:latest`...

Thanks for reporting and providing the sample @Garethp ! I was able to reproduce your observed exception and will reopen this issue.

Hi @vimiomori, I've checked and validated the test you added. During this I've kinda jumped into a bit of a rabbit hole and validated a lot of the other secretsmanager...

Closing this as we currently don't plan to continue with this for the time being and there's not much here that would be hard to recreate (adding a dependency and...

Rebased on master & generated updated snapshots for the parametrized test.

@thrau @alexrashed Would love some input on how to best check for provider/plugin changes. Ideally a minimal set that most likely requires at least a new `make entrypoints`.