Hello everyone! I'm getting the following error at the moment to execute an ingestion from Redsfhit:

acryl.executor.execution.task.TaskError: Failed to resolve secret with name REDSHIFT_HOST_PORT. Aborting recipe execution

. The datasource was created a month ago and it was working good, but since I upgraded my datahub instance to the 0.3.38 version the data ingestion has been broken. I could't find a solution to this exception, I can't read any secret from that ingestion. Is there any consideration that I missed at the moment of the version upgrade? Hope someone can help me! Thanks!

@careful-pilot-86309 *

@busy-machine-97034 Can you share simplified recipe which is causing trouble?

Sure, its really a simple recipe:

source:
    type: redshift
    config:
        host_port: '${REDSHIFT_HOST_PORT}'
        database: prod
        username: '${REDSHIFT_USER}'
        password: '${REDSHIFT_PASSWORD}'
        include_tables: true
        include_views: false
        schema_pattern:
            allow:
                - dwh
                - stg
                - serving
                - '.*_refined'
                - '.*_landing'
        profiling:
            enabled: false
sink:
    type: datahub-rest
    config:
        server: '${DATAHUB_SERVER}'
transformers:
    -
        type: pattern_add_dataset_ownership
        config:
            owner_pattern:
                rules:
                    '.*olimpo_postgres_global_refined.appointment_db.*': ['urn:li:corpGroup:data_business_innovation']
                    '.*olimpo_postgres_global_landing.failure_db.*': ['urn:li:corpGroup:data_business_innovation']
                    '.*olimpo_postgres_global_landing.maintenance.*': ['urn:li:corpGroup:data_business_innovation']
            ownership_type: DEVELOPER

Can you please once confirmed these environment variables are there in the system? Please confirm if value of REDSHIFT_HOST_PORT is a number and don't contain any special characters

Yes, the secrets already exists and the value does not contain special characters

Let me do some more investigation. Will get back

@busy-machine-97034 Can you try steps mentioned in below thread and let me know how it goes for you. The thread is for the exact same error message: https://datahubspace.slack.com/archives/C029A3M079U/p1648137419315219