Container Handlers: Force redeploy if the container is updated

[ianrothmann]

Hi there,

Thanks for the wonderful package. It really saves lives 😎

I have a use case where I use a container and so in my handler function, I return Package::CONTAINER_HANDLER;

The page contains the ImageUrl with tag :latest.

It happens that the container code gets updated, but sidecar refuses to redeploy because of the below code in LambdaHandler.php (line 143 - I commented this line). This is because the ImageUri is still exactly the same, but the container has been updated.

Would it be possible that we can add a flag to the command to force a redeploy?

Kind regards,

Ian

[aarondfrancis]

Thanks for opening an issue! Is this the same as this issue: #67?

If so, can you think of a generalized solution that would work? I don't deploy containers so I'll admit I'm not fully up to speed on their workings, but I would like to fix this.

[ianrothmann]

Indeed it does work. I did:

public function package()
    {
        return [
            'ImageUri' => '...:latest',
            '__handler__' => rand(1,10000), //Ensuring that the package updates
        ];
    }

Thanks for your help!