You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Convert auth to Trusted Publishers for publishing to PyPI instead of using long lived API tokens.
This is really just defining the repo and workflow (and optionally an environment which we could use for our production vs test releases). It uses OIDC to exchange short lived tokens instead of using our long lived tokens. Example workflow in this blog post.
dbt-core
dbt-snowflake
dbt-redshift
dbt-bigquery
dbt-spark
others? look through the packages we release to PyPI and adjust/request maintainers adjust?
The text was updated successfully, but these errors were encountered:
I've looked into this and because the workflows that actually publishes to PyPI lives in another repo (dbt-release) we cannot use this auth method. We should still favor using this method wherever possible.
Convert auth to Trusted Publishers for publishing to PyPI instead of using long lived API tokens.
This is really just defining the repo and workflow (and optionally an environment which we could use for our production vs test releases). It uses OIDC to exchange short lived tokens instead of using our long lived tokens. Example workflow in this blog post.
The text was updated successfully, but these errors were encountered: