bug: Unable to update stack "RemovePermission operation: No policy is associated with the given resource." about localstack HOT 8 OPEN

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

from localstack.

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

from localstack.

I have the same issue

from localstack.

I also think this is related to this other issue somehow: #10042

Because using the same workaround I mentioned there, it works

from localstack.

Same issue here when running samlocal deploy

from localstack.

I pulled down the latest image and am still seeing this issue on 3.1.1.dev20240222103119. Has this fix been pushed up to docker yet?

from localstack.

@dominikschubert I'm still seeing this error on 3.1.1.dev20240223125541, which was published an hour ago. Instead of being on APIGateway Integrations, I've reproduced it for Event Rule Targets, with the following code:

export class LambdaPermissionStack extends Stack {
  constructor(scope: Construct, id: string, props: StackProps) {
    super(scope, id, props);

    const lambda = new Function(this, "lambda-handler", {
      runtime: Runtime.NODEJS_20_X,
      code: Code.fromInline("exports.handler = async () => ({ });"),
      handler: "index.handler",
    });

    new Rule(this, "ScheduleRule", {
      schedule: Schedule.cron({
        hour: process.env.SECOND_RUN ? "7" : "6",
        minute: "0",
        weekDay: "MON-FRI",
      }),
      targets: [new aws_events_targets.LambdaFunction(lambda)],
    });
  }
}

I've pushed a reproduction up to: https://github.com/Garethp/localstack-bugs/tree/lamda-permission-redeploy, just clone down that branch, run yarn install && ./start.sh and you should see the error occur.

from localstack.

Thanks @dominikschubert, that update works for my stack :)

from localstack.