I have a project that I am having issues with since the new release. # Dependencies The client itself is

cargo-shuttle 0.7.0

with my

Cargo.toml

having:

shuttle-secrets = "0.7.0"
shuttle-service = { version = "0.7.0", features = ["bot-serenity"] }
shuttle-shared-db = { version = "0.7.0", features = ["postgres"] }

# Commands ## Reset everything

cargo shuttle project rm
cargo shuttle project new

The listing

cargo shuttle deployment list

confirms that I have some past deployment with these resources: -

database::shared::postgres

-

No secrets are linked to this service

<- that one is not normal, I have a

Secrets.toml

## Deletion When I try to delete those with

cargo shuttle delete

I get:

Error: 500 Internal Server Error
message: Persistence failure: Database error: error returned from database: (code: 787) FOREIGN KEY constraint failed

My current database is empy (no data, no table) and my project do not have any FK for now. ## Deployment If I try to push my code with

cargo shuttle deploy

, the

secret_store

crate fails to find stuff from my

Secrets.toml

(probably linked to the previous No secrets are linked to this service). If you have any idea how to make those two commands work again, it would be greatly appreciated 🙏.

Hey 👋 , there are a bunch of things happening here at once: 1. Currently having

Secrets.toml

in .gitignore causes them to not be archived. Hence why they are not set. This is a known issue we have an open ticket for. So should get to it soonish. 2. The foreign key constraint is an internal shuttle error on our deployments database. This one is currently not that high on our fix list (having some other emergencies 😅 ) but it will also get fixed. The current idea with

cargo shuttle delete

is to only stop the running deployment and not delete all resources. TL;DR; the deploy should work by temporarily removing

Secrets.toml

from

.gitignore

1. Ah! I saw this in another thread but I did not make the connection, sorry about that 😬 2. Alright, thank you for the explanation 🙇 And thank you for reminding me of gitignore workaround!

With the new release the gitignore workaround should no longer be needed 🥳

Good news! I'll try to hunt down the specific commit/PR for my own curiosity. I would love to help out on small things but my Rust knowledge is embarrassing at the moment :)