search

Azure / service-fabric-mesh-preview

Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
MIT License
82 stars 11 forks source link

Can an sf application be forcefully overwritten? #330

Closed damienestewart closed 5 years ago

damienestewart commented 5 years ago

It seems that an sfmesh application is only redeployed when there are changes to the settings, which makes complete sense. In my case, I made code changes and rebuilt my docker image with the same exact name and tag. When I tried to redeploy, expecting the sf app to be updated, it wasn't. I suspect that it's because the settings didn't change due to using the same image name/tag.

Is this intended behavior? Is it mandatory to change the docker image tag for a scenario like this, or is there a way to force the redeployment?

guibirow commented 5 years ago

The correct way is updating the tags on every change, maybe use the build number as tag, because you did use the same tag, the engine used the cached version already in the host. This is one of the reasons you should not use latest or omit the tags when deploying a container.

I don't think there is a "force" update option. Right now we can't even restart the container :(

damienestewart commented 5 years ago

I see, thanks for the awesome input @guibirow!

raunakpandya commented 5 years ago

Hope the answer clarifies. Closing the issue..