Reuben

> I think ideally and I didn't mention this option above, we could do something similar to what `meltano run` or `meltano el` do under the hood and populate a...

I'm finding this a bit hard to follow, but are there not two separate issues here: 1. Plugin contexts are not shared at install time ```sh env -i PATH="$PATH" HOME=$HOME...

> I'm currently looking for same use case - i'd like to convert all column names to lower case (source is tap-mssql, and loader is target-postgres). In my case tables...

> ```yml > stream_maps: > '*': > __alias__: __property_name__.lower() > ``` I now realise that this conflicts with stream aliasing as currently implemented, so perhaps it would need to follow...

Would you accept a PR to partially implement stream aliasing via stream maps (`__alias__`) for `BATCH` messages? https://github.com/Matatika/tap-bigquery/commit/9c96860aaa1439c1560a4ca62a0beb2040c1f368

> ```console > $ TAP_PYPISTATS_PACKAGES='["meltano"]' meltano config tap-pypistats--2 list > 2025-04-29T18:45:10.671531Z [info ] The default environment 'dev' will be ignored for `meltano config`. To configure a specific environment, please use...

> ```console > $ TAP_PYPISTATS__2_PACKAGES='["meltano"]' meltano config tap-pypistats--2 list > 2025-04-29T19:44:39.604632Z [info ] The default environment 'dev' will be ignored for `meltano config`. To configure a specific environment, please use...

> Ok, I finally see what you mean 🙈. > > I'm not sure what the right solution is here. It does seem like what you describe _should_ be the...

This seems to be the intended behaviour when using `AnyType`: https://github.com/meltano/sdk/blob/2874a15abefff83a994dc0e3b2805f660e0e0bf6/tests/core/test_jsonschema_helpers.py#L183-L186 Not sure why this is the case. The main issue here is the amount of times this warning message...

Thanks, that reduces the amount of warnings significantly (once for each stream with a schema referencing `AnyType`): ``` $ meltano invoke tap-capsulecrm 2>&1 | grep -c 'Could not append type'...