Francesco Landini
07/24/2025, 2:29 PMedr report --profiles-dir . but I got this error: The profile 'elementary' does not have a target named 'redshift'. The valid target names for this profile are:
- type
- host
- user
- password
- dbname
- schema
- port
- sslmode
- ra3_node
- autocommit
- threadskapa.ai
07/24/2025, 2:29 PMkapa.ai
07/24/2025, 2:29 PMyaml elementary: outputs: default: type: redshift host: <your_host> user: <your_user> password: <your_password> dbname: <your_dbname> schema: <your_schema> port: <your_port> threads: 1 target: default - The key under outputs (here, default) is the target name. - All connection parameters should be nested under that target. - The target field at the same level as outputs tells Elementary which target to use by default. If you want to use a different target name (e.g., redshift), define it like this: yaml elementary: outputs: redshift: type: redshift host: <your_host> user: <your_user> password: <your_password> dbname: <your_dbname> schema: <your_schema> port: <your_port> threads: 1 target: redshift Then, you can run: edr report --profiles-dir . -t redshift This structure is required for Elementary to recognize the target and its connection parameters correctly. For more details and examples, see the related discussion [here](https://slack.com/archives/C02CTC89LAX/p1686013979045139). If you fix your profiles.yml as shown above, the error should be resolved.