Stefano
Stefano
Maybe mounting an EFS volume for persistent storage might help?
Thanks for the heads up, I'll check ASAP
See https://github.com/cgauge/Flask-AWSCognito/issues/13
Hopefully someone with `write` access will merge it soon, I'm not longer a maintainer of this repository
I got it working by persisting a session and updating its headers (also the 'Referer' one): ```python import requests BASE_URL = '...' # your base Superset URL LOGIN = '/api/v1/security/login'...
> Thanks for reaching out [@nathangriffiths-cdx](https://github.com/nathangriffiths-cdx) ! > > Is your request basically that the SQL for snapshots would be written to `target/compiled/your_project/snapshots/` when you run `dbt compile`? Yes this...
+1 for this feature. We are stumbling on this problem as well, this approach: ``` version: 2 models: - name: my_model config: contract: enforced: true columns: &common_columns - name: composite_id...
I understand @genzgd thanks for your reply. So I guess at the moment `dbt-clickhouse` uses `clickhouse-connect`, can you point me to where the magic happens? I.E. how the credentials are...
@genzgd thanks a lot for the info. I'll have a look. So you're saying changes would need to happen in two places? The second link is pointing to the same...
@genzgd it seems the `clickhouse_driver.Client` supports the `keyfile`: ```python chc = Client( host='', secure=True, user='', keyfile='' ) chc.execute('SHOW DATABASES') ``` though I'm not sure if that's passed along, it seems...