[Bug] Wildcards node selection not working as expected.

[H-Max]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

There seems to be issues with selecting nodes to run when using wildcars.

I have a model name "INT_OH_TOPAZ_PER" and I try to select it (in dbt run / dbt list, dbt whatever) and the following behavior does not seem to be correct:

• dbt list -s "INT_OH_TOPAZ_PER" works
• dbt list -s "INT_OH_TOPAZ_*" does not work (it should)
• dbt list -s "*_OH_TOPAZ_*" works
• dbt list -s "INT_OH_TOPAZ_PE?" does not work (it should)
• dbt list -s "*INT_OH_TOPAZ_PE?" works (it should)

It seems that starting the selection string with a * is mandatory in order for further wildcards to work.

The documentation does not mention this behavior : https://docs.getdbt.com/reference/node-selection/methods

(if it's the expected behavior, then it should be explicitely written in the doc)

Expected Behavior

We should be able to use wildcards without having to start the selector string with "*"

Steps To Reproduce

Create a model and try to select the model in various dbt CLI commands with wildcards in it, following the examples in the behavior description above.

Relevant log output

Environment

- OS: MacOS
- Python: 3.11.x
- dbt: 1.9.2 (core) 1.9.0 (BigQuery)

Which database adapter are you using with dbt?

bigquery

Additional Context

No response