with this change in my profiles.yml:

-      ra3_node: "{{ env_var('DBT_REDSHIFT_RA3_NODE', False ) }}" # optional, enables cross-database sources
+      ra3_node: "{{ env_var('DBT_REDSHIFT_RA3_NODE', 'false' ) == 'true' }}" # optional, enables cross-database sources

Then

DBT_REDSHIFT_RA3_NODE=true meltano invoke dbt-redshift:freshness

correctly returns results for a source in a different database 🦜 I’m not sure if there’s a bug here or not - it seems like setting the

ra3_node

configuration property (whether as a YAML boolean

true

or as a quoted string

True

would be lowercased by the time it was parsed by profiles.yml, and that seemed not to be parsable ? Regardless, I think this will work for me