Hi everyone, i am trying to intstall target-snowflake on a server which sits behind a proxy and the isntallation fails beacause when installing the polugin a call is made to this url: https://i32s35df22.execute-api.us-west-2.amazonaws.com. Does anyone know what this url is? All the other plugins install without any problems. Thanks!

I don't know off hand but my first guess would be a metric's endpoint for one of the libraries. Maybe it's the snowflake library?

I dont think it is about metrics. I saw in the networkm log that it goes first to hub.meltano.com and then after exchanging application data it goes to the url. Same thing also happens with target-postgres which is also from meltano lab

With lock files I don't think it should be happening but I could be wrong. Can you share how you're running this? Meltano.yml and however you're running in production (docker file etc)

I am running it in docker. The pipeline builds the image and it is in the pipeline that it fails. Other plugins like target-jsonl, target-s3 install without any problems. Pipeline runs behind a enterprise proxy and that is why it is blocked. loaders: - name: target-jsonl variant: andyh1203 pip_url: target-jsonl - name: target-snowflake variant: meltanolabs pip_url: meltanolabs-target-snowflake

Can you share the stack trace? And your docker file? Also can you ls your lock file directory.

The lock file is not the problem. I tried installing the plugin directly as a command in the dockerfile still fails. RUN meltano add loader target-snowflake. When i remove the target-snowflake the docker image is builded succefully. Localy it also runs great

Hey @Eni S

RUN meltano add loader target-snowflake

isn't gonna work unless you whitelist

<http://hub.meltano.com|hub.meltano.com>

because Meltano needs to reach the MeltanoHub API to add a plugin. A better approach is to run

meltano add

locally, and then do something like

COPY meltano.yml meltano.yml
COPY plugins/ plugins/

But hub.meltano is already whitelisted

> For other Plugins not from meltanolabs there are no problems. Do they go through another api? They all go through the same MeltanoHub API, so I'm not sure what's going on there. > I would still like to understand why the second call to https://i32s35df22.execute-api.us-west-2.amazonaws.com is maid. I had a look at wireshark and i saw that the first request goes to hub.meltano.com and then the second to the above url. It's a simple redirect. The API is hosted on S3 and proxied through API Gateway and a redirect is configured on Netlify for historical reasons.

Thank you! @Edgar Ramírez (Arch.dev)