You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with Client Extensions, running deploy can mess with the resources. It seems that the proper way to update a Client Extension is to run a clean deploy instead.
Therefore, it would be practical to have a clean flag to the lfr deploy command (and its shortcut lfr d) to avoid writing lfr x clean deploy.
Being able to have this flag in the configuration (e.g. deploy.clean=true to automatically run the clean arguments when running the deploy command would be a plus. It would be similar to the logs.follow=true that allows to write lfr logs instead of lfr logs -f if we always want to follow logs.
The text was updated successfully, but these errors were encountered:
When working with Client Extensions, running
deploy
can mess with the resources. It seems that the proper way to update a Client Extension is to run aclean deploy
instead.Therefore, it would be practical to have a clean flag to the
lfr deploy
command (and its shortcutlfr d
) to avoid writinglfr x clean deploy
.Being able to have this flag in the configuration (e.g.
deploy.clean=true
to automatically run the clean arguments when running the deploy command would be a plus. It would be similar to thelogs.follow=true
that allows to writelfr logs
instead oflfr logs -f
if we always want to follow logs.The text was updated successfully, but these errors were encountered: