@kurt I too am having this issue. I’ve not changed my secrets in 60 days. In the last 15 days I’ve not been able to modify my secrets and the error returned is the same.
@gorka@rhodee you both should be set now, will you give it another try? Our database and the vault instance we store secrets in was out of sync for one of your apps.
Also, @gorka, I apologize for missing this last week.
It worked out fine for a couple of tries but then the deployment got stuck at
Release v2 created
You can detach the terminal anytime without stopping the deployment
Monitoring Deployment
1 desired, 1 placed, 1 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
and then I stopped the process with ctrl + c (SIGINT) (maybe this? but it shouldn’t cause that from what I understand) and after that none of the secrets commands were working
../flyctl/bin/flyctl secrets import < .env
map[MY_CERT:"-----BEGIN CERTIFICATE-----\nMIIFaz... etc ...FfLn\n-----END CERTIFICATE-----\n"]
Error Could not resolve VaultSecret
diru@pop-os:~/Desktop/go-api$ ../flyctl/bin/flyctl secrets import < cert.env
map[MY_CERT:"-----BEGIN CERTIFICATE-----\nMIIFaz... etc ...FfLn\n-----END CERTIFICATE-----\n"]
Error Could not resolve VaultSecret
diru@pop-os:~/Desktop/go-api$ ../flyctl/bin/flyctl secrets list
Error Could not resolve VaultSecret
and later I saw that the app was crashed/dead, the same error persisted when I recreated the app.
hope it helps, just wanted to point it out as I wasn’t sure where the error was coming from.