search

beamable / BeamableProduct

The beamable product suite including com.beamable, com.beamable.server, microservice base image, portal, the installer, and build scripts
Other
5 stars 0 forks source link

CLI - services deploy should have overwrite flag #3412

Open cdhanna opened 4 months ago

cdhanna commented 4 months ago

internal discussion- https://disruptorbeam.slack.com/archives/C03P1J5NR97/p1716410793532369?thread_ts=1716408419.099319&cid=C03P1J5NR97

Today, if you have a remote-only service, and you do

beam services deploy

then the remote only service is left AS IS, and nothing happens to it.

However, it would be nice to offer a flag, --overwrite that allows you to ARCHIVE everything on the remote that isn't part of the current local source. If anything is detected as ready to get archived, we should issue a confirmation to the user, and allow them to back out of the operation.

Additionally, we should add a --force flag that disables those confirmations.

cdhanna commented 4 months ago

it would be nice to have explicit switches like this

beam services enable-remote-thing --ids ToastTruck,Fish

Alternatives to --overwrite

  1. --archive-remote
# this is similar to --overwrite
beam services teardown-everything-on-the-server
beam services deploy

What about...

  1. whole replacement
  2. single service deployment / single service removal
  3. additive deployment
beam deploy --additive 
beam deploy --overwrite
beam deploy TunaTruck --disable # turn off TunaTruck, and do nothing else
beam deploy TunaTruck --enable # turn on TunaTruck, and do nothing else
beam deploy plan -o plan.json
beam deploy fire plan.json

beam deploy