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
We are running several checks in our CI that currently require a charmhub token to authenticate. This limits community contributions given that forks would require their own token.
The operations we are executing are currently list-lib and fetch-lib, which expose information that is already publicly available. Could authentication be removed from these? Also, it would probably make sense to do the same for querying revisions, resource-revisions and status.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi!,
We are running several checks in our CI that currently require a charmhub token to authenticate. This limits community contributions given that forks would require their own token.
The operations we are executing are currently
list-lib
andfetch-lib
, which expose information that is already publicly available. Could authentication be removed from these? Also, it would probably make sense to do the same for queryingrevisions
,resource-revisions
andstatus
.Thank you!
The text was updated successfully, but these errors were encountered: