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
Ah, the new argument has a default of "True," so you can choose to turn that off by setting it equal to False. If you think it is strongly expected to be False, I can either update it or remove the default altogether. 👍
You are correct! I originally had thought there was something else going wrong. Upon further review, it looks like rsconnect.deploy_python_fastapi will think that every deployment is "new." When a model is sent to connect with deploy_rsconnect, it is deployed from a temporary directory where an app.py file is created from a pinned model. This temporary directory holds the manifest JSON file that would normally be used to determine if the deployment was "new" or not. An escape hatch out of this not-actually-new behavior that currently exists is to supply an app_id, which will force-overwrite the existing content.
I'll have to peek into rsconnect to see what validating newness looks like 👀
Describe the bug
using
rsconnect_deploy
to redeploy an existing API on Connect, it deploys a new API. I did not specify thenew
argument eitherTo Reproduce
Use can use the jupyter notebook published here.
Expected behavior
Redeploying an existing API should overwrite the existing content.
The text was updated successfully, but these errors were encountered: