-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor CLI setup #194
Refactor CLI setup #194
Conversation
@click.option( | ||
"--http_extra_headers", | ||
cls=OptionAcceptableFromConfig, | ||
type=(str, str), | ||
multiple=True, | ||
help="Additional HTTP request header to be sent to Metabase.", | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, I see that this part has been removed from the new version 1.0.0, is it expected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still available in the programmatic API. I couldn't get the dictionary type to work via CLI flag, were you using it via config YAML file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Released in v1.0.1, you can now use:
dbt-metabase [COMMAND]
--http-header x-some-header-1 some-value-1
--http-header x-some-header-2 some-value-2
or via YAML config:
config:
http_headers:
- [x-some-header-1, some-value-1]
- [x-some-header-2, some-value-2]
That was fast, thank you 🙏 |
--dbt_database
becomes--dbt-database
)--dbt-includes model1 model2
becomes--dbt-includes model1,model2
)METABASE_
instead ofMB_
dbt-metabase config
)--dbt-path
is now--dbt-project-path
)dbt-metabase --config-file path/to/config.yml models
)script
toentry_points
in setup.py for better cross-platform support