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
On running snow streamlit deploy --replace, the current set of files in local env should be moved to Snowflake Internal Stage and the deleted files from local should get removed from internal stage.
Currently the files deleted from local still persists within the Snowflake Internal Stage.
Console output
No response
How to reproduce
Deploy a streamlit app with some sets of files.
Remove/Rename some files and re deploy.
Existing removed/renamed files will still exists in Snowflake
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
snow streamlit deploy --replace doesn't remove deleted files from the internal stage
SNOW-1634816: snow streamlit deploy --replace doesn't remove deleted files from the internal stage
Aug 21, 2024
A customer surfaced this issue a few days ago as the orphaned objects left in the stage caused unexpected behavior. Perhaps we iterate through the staged files to check if they are still in the project? Or add a --clear-stage flag to remove all files before deployment? Would likely need a "protected files" manifest to prevent removal of files in the stage that may be used to maintain state, etc.
SnowCLI version
2.7
Python version
Python 3.9.10
Platform
Linux-5.15.153.1-microsoft-standard-WSL2-x86_64-with-glibc2.31
What happened
On running snow streamlit deploy --replace, the current set of files in local env should be moved to Snowflake Internal Stage and the deleted files from local should get removed from internal stage.
Currently the files deleted from local still persists within the Snowflake Internal Stage.
Console output
No response
How to reproduce
Deploy a streamlit app with some sets of files.
Remove/Rename some files and re deploy.
Existing removed/renamed files will still exists in Snowflake
The text was updated successfully, but these errors were encountered: