Skip to content
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

Allow API token to be scope to multiple projects #12176

Closed
ashb opened this issue Sep 5, 2022 · 4 comments
Closed

Allow API token to be scope to multiple projects #12176

ashb opened this issue Sep 5, 2022 · 4 comments
Labels
blocked Issues we can't or shouldn't get to yet feature request organizations

Comments

@ashb
Copy link

ashb commented Sep 5, 2022

Hello, I'm a member of the core team for Apache Airflow, and we have our project split up in to a number of distributions on PyPI - the core "apache-airflow" dist and (currently, but it grows over time) 70 provider modules, apache-airflow-providers-*.

I would like to be able to "easily" upload those provider dists via API tokens, but currently I either need to use an account-wide token, or each upload needs a separate API key (which doesn't easily work for our normal release workflow, where we will release all provider packages with changes once a month)

It's possible Organizations might help here if it's possible to have an Org-wide API token?

Relates to #7265

@ashb ashb added feature request requires triaging maintainers need to do initial inspection of issue labels Sep 5, 2022
@dstufft
Copy link
Member

dstufft commented Sep 5, 2022

You can create an account wide token, then scope it yourself for multiple projects if that works for you, although I do agree ti would be nice for our UI to support multiple of them here.

@di di added blocked Issues we can't or shouldn't get to yet organizations and removed requires triaging maintainers need to do initial inspection of issue labels Sep 23, 2022
@di
Copy link
Member

di commented Sep 23, 2022

Hi, thanks for the issue. We agree this is a good idea, and that it's going to be much easier to implement to implement for organizations/teams once that feature has landed, so we'll consider this blocked on #11590.

@Julian
Copy link
Contributor

Julian commented Mar 17, 2023

Is this a duplicate of #6292 perhaps?

@di
Copy link
Member

di commented Mar 17, 2023

Yep! Duplicate of #6292.

@di di closed this as completed Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Issues we can't or shouldn't get to yet feature request organizations
Projects
None yet
Development

No branches or pull requests

4 participants