denis_gribanov
07/21/2023, 3:17 PM--log-level=debug
option:
2023-07-21T15:10:10.081783Z [debug ] Looking for endpoint for s3 via: environment_global
2023-07-21T15:10:10.081891Z [debug ] Looking for endpoint for s3 via: config_service
2023-07-21T15:10:10.081994Z [debug ] Looking for endpoint for s3 via: config_global
2023-07-21T15:10:10.082107Z [debug ] No configured endpoint found.
Also you can notice the variable for an endpoint in Github: https://github.com/meltano/meltano/blob/main/integration/meltano-state-s3/validate.sh
Has anyone used this option? How do we provide it to Meltano?edgar_ramirez_mondragon
07/21/2023, 4:41 PMdenis_gribanov
07/21/2023, 4:44 PMdenis_gribanov
07/21/2023, 6:16 PMMELTANO_STATE_BACKEND_S3_ENDPOINT_URL
variable to specify the endpoint, but it’s no luck— it falls back to the default aws endpoint:
2023-07-21T18:09:26.558534Z [debug ] Looking for endpoint for s3 via: environment_service
2023-07-21T18:09:26.558688Z [debug ] Looking for endpoint for s3 via: environment_global
2023-07-21T18:09:26.558844Z [debug ] Looking for endpoint for s3 via: config_service
2023-07-21T18:09:26.558945Z [debug ] Looking for endpoint for s3 via: config_global
2023-07-21T18:09:26.559068Z [debug ] No configured endpoint found.
Though MELTANO_STATE_BACKEND_S3_ENDPOINT_URL
persists in the.env file as well as a global variable.
Am I missing something? Could you please point me in the right direction? We’re using Meltano 2.20.0 with tap-postgres and target-postgres (both meltanolabs variant)edgar_ramirez_mondragon
07/21/2023, 6:24 PM$ meltano config meltano list | grep ENDPOINT_URL
state_backend.s3.endpoint_url [env: MELTANO_STATE_BACKEND_S3_ENDPOINT_URL] current value: None (default)
denis_gribanov
07/21/2023, 6:28 PMmeltano config meltano list | grep ENDPOINT_URL
2023-07-21T18:27:04.153719Z [info ] Environment 'prod' is active
state_backend.s3.endpoint_url [env: MELTANO_STATE_BACKEND_S3_ENDPOINT_URL] current value: '<https://custom_provider.com>' (from the MELTANO_STATE_BACKEND_S3_ENDPOINT_URL variable in the environment)
Though credentials can be found in the environment:
2023-07-21T18:30:36.370586Z [debug ] Looking for credentials via: env
2023-07-21T18:30:36.370766Z [info ] Found credentials in environment variables.
edgar_ramirez_mondragon
07/21/2023, 7:19 PMMELTANO_STATE_BACKEND_S3_ENDPOINT_URL
is correctly used when I set it in .env
(I do get an "Invalid endpoint: https://custom_provider.com" error). Are you running all commands in the same shell?denis_gribanov
07/21/2023, 7:35 PMedgar_ramirez_mondragon
07/21/2023, 7:57 PMian_lewis
07/24/2023, 8:56 AMMELTANO_STATE_BACKEND_URI='<s3://my-data-lake/>'
This works for me.denis_gribanov
07/24/2023, 8:59 AMian_lewis
07/24/2023, 9:24 AM