Skip to content

Fix config parsing - #91

Merged
Gerrrr merged 1 commit into
masterfrom
bug-88/autocomplete-only-importer-specific-config
Sep 9, 2025
Merged

Gerrrr merged 1 commit into
masterfrom
bug-88/autocomplete-only-importer-specific-config

Conversation

@Gerrrr

@Gerrrr Gerrrr commented Sep 7, 2025

Copy link
Copy Markdown
Contributor

This fixes #88 . Now, the CLI parser ignores sections of the config that do not have their equivalents in the CLI.

Now, the CLI parser ignores sections of the config that do not have
their equivalents in the CLI.

@smccarthy788 smccarthy788 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this 😄

@Gerrrr
Gerrrr merged commit 484aaef into master Sep 9, 2025
3 checks passed
Gerrrr added a commit that referenced this pull request Nov 28, 2025
Gerrrr added a commit that referenced this pull request Nov 28, 2025
* Revert "Fix multiple issues discovered via running examples (#95)"

This reverts commit 5276f24.

* Revert "Fix config parsing (#91)"

This reverts commit 484aaef.

* Revert "OTAVA-82: use ConfigArgParse to create Config (#86)"

This reverts commit 69d2b97.

* Fix docker run commands in examples

* Bump year in the postgres example data

By default, Otava looks 1 year back. Example data is too old.

* Update CLI help description

* Add e2e tests covering CSV and PostgreSQL usage

* OTAVA-65: Fix --help requiring a config file

* Run tests against branch 0.7

* Fixup csv docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PostgreSQL importer does not work with new config parsing

2 participants