Skip to content

Bug: Source config with non-existent tables should report an error or warning #2312

@hermanschaaf

Description

@hermanschaaf

Currently, if you have a source config lists tables that are not defined, no warnings or errors are logged. In the worst case, this can lead to 0 resources being fetched due to misconfiguration, but no error to explain why.

The CLI should at least report a warning when this happens, and probably error out completely if zero resources match the definitions.

Version tested: cli-v1.3.0-pre.1

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions