Relationships
#1561 swamp command doesn't check cwd
Opened by svendowideit · 8/8/2026
so, I might have made my own bed with that previous "walk the path to find the .swamp dir" issue, but ..
sven@x1yoga:~/src/swamp-project/extensions/workflows/news-workflow$ swamp extension push manifest.yaml
Error: Manifest file not found: /home/sven/src/swamp-project/manifest.yaml
sven@x1yoga:/src/swamp-project/extensions/workflows/news-workflow$ pwd
/home/sven/src/swamp-project/extensions/workflows/news-workflow
sven@x1yoga:/src/swamp-project/extensions/workflows/news-workflow$ swamp extension push extensions/workflows/news-workflow/manifest.yaml
2026-08-08T13:27:40.404Z
which is to say - the opposite would be nice to just work too - if i'm in a sub dir, and specify a file path, swamp should figure out the .swamp stuff, but also still consider the cwd for that path :)
sorry
Closed
No activity in this phase yet.
stack72 commented 9/14/2026, 6:10:10 PM
Hey @svendowideit
Thanks for the report. This is supported today by setting the extension source directory explicitly:
cd extensions/workflows/news-workflow
swamp extension push --extensions-dir . manifest.yamlSwamp will still locate the repository's .swamp.yaml by walking up from the current directory. --extensions-dir . tells Swamp that the current directory is the extension source base, so the manifest and its extension files resolve from there.
If the extension source is instead rooted at the repository root, continue to pass a repository-relative or absolute manifest path. We do not plan to make relative manifest paths implicitly CWD-relative, since that would change existing repository-relative invocations depending on where they are run.
Sign in to post a ripple.