Donal McBreen
Donal McBreen
Hi @lewispb - we've got a test failure on `test/integration/app_test.rb:23`
Closing in favour of #980 as that has more detail
This should be resolved in Kamal 2, though the secrets are now in `.kamal/secrets` rather than `.env`. You can get either behaviour: ``` #.kamal/secrets FOO=$FOO # reads from environment FOO=value...
Not requiring the secrets allows someone to run `kamal app exec` without having access to the secrets manager set up. This means you can do things like giving someone access...
> Not requiring secrets is certainly beneficial, that's how I want Kamal to be too. This PR doesn't change that; if you haven't set any secrets, the behavior remains the...
Yeah an option makes sense here - we can add a boolean `--push-secrets` to `kamal app exec` defaulting to false.
Could you provide more context from the logs for your error? What command is it running that produces it?
Thanks @kczpl! If the deployments sometimes pass succeed then your configuration sounds like it should be ok. Maybe the containers are taking too long to boot and hitting the deployment...
Thanks for reporting this @fabiendv! As a workaround, you can set the build context to `.` which will build directly from the checkout but will include any uncommited changes.
The original issue should be fixed by https://github.com/basecamp/kamal/pull/889