stegus64
03/04/2026, 11:49 AMtype: api
spec: "local/C:\BIPROD\BI_Runtime\Environments\Prod\slinghome\api_spec_releasy.yaml"
The effect of this was that sling could not find any connections at all. No parsing error messages.
sling conns list suddenly listed nothing.
We know now that it should be written like this instead:
type: api
spec: "local/C:/BIPROD/BI_Runtime/Environments/Prod/slinghome/api_spec_releasy.yaml"
Finding this was not easy. Maybe you should add some more informative error messges?
Also, it would be nice with a trace-level log that shows what places are searched for the env.yaml file, and the path of the file that is actually used.
And a question: When you use a relative spec like
spec: "local/api_spec_releasy.yaml"
Where does it look for this file? Is it relative to the current working folder, or the env file, or the replication file?flarco
03/04/2026, 11:53 AMfile:// prefix, so file://relative/file.yaml and file:///absolute/path/to/file.yamlflarco
03/04/2026, 11:54 AMstegus64
03/04/2026, 11:55 AMflarco
03/04/2026, 11:56 AMstegus64
03/04/2026, 11:57 AMstegus64
03/04/2026, 11:57 AMstegus64
03/04/2026, 11:59 AMflarco
03/04/2026, 12:00 PM$SLING_HOME_DIR in the spec path to do relative from there. but yea, other users for example save their spec path in the repo, and use absolute path from CWDstegus64
03/04/2026, 12:02 PMstegus64
03/04/2026, 12:05 PMflarco
03/04/2026, 12:05 PMflarco
03/04/2026, 12:10 PM--home-dir flagstegus64
03/04/2026, 12:10 PMstegus64
03/04/2026, 12:14 PMflarco
03/04/2026, 3:04 PMconvertkit:
type: api
spec: file://${SLING_HOME_DIR}/test_convertkit.yaml
So you'll need ${SLING_HOME_DIR}
along with --home-dir /tmp/sling-test-homestegus64
03/04/2026, 3:13 PMstegus64
03/04/2026, 3:14 PMflarco
03/04/2026, 3:40 PM