CLI - services coming back to life after deploy

beamable / BeamableProduct

The beamable product suite including com.beamable, com.beamable.server, microservice base image, portal, the installer, and build scripts

Other

3 stars 0 forks source link

CLI - services coming back to life after deploy #3493

Open gabrielbeamable opened 2 weeks ago

gabrielbeamable commented 2 weeks ago

Have 1 or more services deployed to your realm
delete those services locally
Go to the portal and stop and archive all of those services
Create a new service
Deploy that service
Notice that all services previously archived, are now unarchived, but still stopped

They don't exist locally and I checked and their ShouldBeEnabledOnRemote property is set to false as it should. However after the deploy, they all come back to life. Going to create an issue for this.

cdhanna commented 2 weeks ago

This is likely because we aren't passing the archived flag along in the manifest, in the WriteServiceManifestFromLocal method.

I think we should change this publish flow to use the autogenerated beamo api code, so that we get the archived flag in sync.