many-farmer-43903
12/22/2020, 3:20 PMinstall
when it is trying to install my custom plugin, any general guidance on troubleshooting? I feel like I'm going in circles
Installing loader 'target-s3-jsonl'...
ERROR: ./target-s3-jsonl is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with svn+, git+, hg+, or bzr+).
data-integration/
meltano.yml
DockerFile
...
target-s3-jsonl/
target_s3_jsonl/__init__.py
meltano.yml snipped:
loaders:
- name: target-s3-jsonl
namespace: target_s3_jsonl
pip_url: -e ./target-s3-jsonl
executable: target-s3-jsonl
capabilities:
- catalog
- discover
- properties
settings:
- name: aws_access_key_id
- name: aws_secret_access_key
- name: s3_bucket
- name: s3_key_prefix
meltano install loader target-s3-jsonl
pip_url
is not defined correctlyripe-musician-59933
12/22/2020, 5:15 PMtarget-s3-jsonl
directory is missing when meltano install
is run as part of the Dockerfile: https://gitlab.com/meltano/files-docker/-/blob/master/bundle/Dockerfile#L12.
As you can see there, only meltano.yml
is copied before running `meltano install`: https://gitlab.com/meltano/files-docker/-/blob/master/bundle/Dockerfile#L11, and all other files are copied later: https://gitlab.com/meltano/files-docker/-/blob/master/bundle/Dockerfile#L21
Since you want target-s3-jsonl
to already be available when meltano install
is run, you'll have to add a new COPY
directive ahead of it:
COPY ./target-s3-jsonl ./target-s3-jsonl/
Ifis a directory, the entire contents of the directory are copied, including filesystem metadata.<src>
Note
The directory itself is not copied, just its contents.
many-farmer-43903
12/22/2020, 5:54 PM