Meltano: the declarative code-first data integration engine that powers your wildest data and ML-powered product ideas. Say goodbye to writing, maintaining, and scaling your own API integrations.
The plugin's executable should reference a local script called tap-mytest.sh in the same directory as meltano.yml (i.e. ./tap-mytest.sh).
Issue Description
Meltano is not able to locate the executable when specified using any of the following forms: ./tap-mytest.sh,tap-mytest.sh, or$MELTANO_PROJECT_ROOT/tap-mytest.sh`.
Meltano can correctly locate the executable if specified as a fully-qualified path (i.e. /path/to/source/tap-mytest/tap-mytest.sh).
For portability, we would want to be able to reference a locally-available executable either by relative reference or using the $MELTANO_PROJECT_ROOTenvironment variable, or both.
According to the docs here, it appears that the environment variable is available in config section, but perhaps not also in the executable property.
MeltyBot
commented
2 years ago
Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2698
Originally created by @aaronsteers on 2021-04-05 23:35:40
As part of https://gitlab.com/meltano/singer-sdk/-/merge_requests/52, there is a need to provide a path to a plugin executable which is not available on PATH or within a meltano-managed virtual environment.
Scenario
The plugin's executable should reference a local script called
tap-mytest.shin the same directory asmeltano.yml(i.e../tap-mytest.sh).Issue Description
./tap-mytest.sh,tap-mytest.sh, or$MELTANO_PROJECT_ROOT/tap-mytest.sh`./path/to/source/tap-mytest/tap-mytest.sh).$MELTANO_PROJECT_ROOTenvironment variable, or both.configsection, but perhaps not also in theexecutableproperty.