env_var should be optional when a user is not passing a yaml file

[chriscardillo]

Is your feature request related to a problem? Please describe.
Users utilizing the warehouse_yml_dict option in ScanBuilder should not be constrained to have to use the env_var parameter. If they're using a dict, they're most likely pulling in sensitive information from the environment anyway.

Describe the solution you'd like
Two options include:

• If the dict is used instead of a yaml, Soda's parser should not run any kind of env_var checks in on the user input.
• Support SQLAlchemy connection objects, where the user can provide you most/all warehouse details Soda requires.

Additional context
N/A

Soda SQL Version: 2.0.0b21

[tombaeyens]

I think that usage of env_var(...) should always be optional. Both in YAML as well as dict.

The way you phrase it it looks like env_var(...) is required. Is that what you experienced?

Would ensuring the env_var resolving is optional, solve your problem?

[chriscardillo]

Yes, it appears that env_var(...) is currently required for anything Soda considers a credential (e.g. a password) and raises an error if a credential field is used without env_var(...).

[tombaeyens]

I m changing it so that env_var is not required.

[vijaykiran]

Fixed!