Validate dbt resource identifier to see if it is a valid airflow task id during conversion from dbt to Airflow

[tatiana]

While parsing the dbt project, we should confirm if the node names we'll use to define Airflow task IDs are valid.
If they are not valid, we should at least raise a warning (probably an error message) explaining the issue to users.

We can accomplish this by using airflow.utils.helpers.validate_key.

This task is related to #636, but they are not duplicates and should not conflict.

This improvement came from a conversation with @MrBones757 , regarding Cosmos 1.2.2. More details:

When we create dbtNode objects in https://github.com/astronomer/astronomer-cosmos/blob/main/cosmos/dbt/graph.py#L367

We set the nodeName == alias, with a fallback to name if it doesn't exist.

We then create the airflow graph with that value here: https://github.com/astronomer/astronomer-cosmos/blob/main/cosmos/airflow/graph.py#L125

The issue: dbt doesn't impose limitations on node names, but airflow does as such. When we go to render the airflow dag in the UI, we get:

The key 'my$cool_alias' has to be made of alphanumeric characters, dashes, dots and underscores exclusively

[tatiana]

For some reason, I'm not being able to assign this issue to @MrBones757 in the Github UI, but he is planning to work on this!

[MrBones757]

Before implementing this, i will wait on #636 to ensure there are no clashing changes.

[tatiana]

@MrBones757 #662 has a first level of "validation" (conversion from dots to underscore)

[dosubot]

Hi, @tatiana,

I'm helping the Cosmos team manage their backlog and am marking this issue as stale. The issue involves validating dbt resource identifiers to ensure they comply with Airflow task ID requirements during the conversion process. It seems that there are plans to work on this, with @MrBones757 expressing intent to address it and waiting for progress on another related issue to avoid conflicts. Additionally, there's a preliminary level of "validation" related to this issue in another open matter (#662).

Could you please confirm if this issue is still relevant to the latest version of the Cosmos repository? If it is, please let the Cosmos team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days.

Thank you for your understanding and cooperation. If you have any questions or need further assistance, feel free to reach out to me directly.