Cant execute npm install if the package comes from a different organization using github app token #129330
Unanswered
lloydsanchez1201
asked this question in
Packages
Replies: 1 comment 2 replies
-
Maybe my project could solve your use case, have a look at https://github.com/qoomon/actions--access-token |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
Hi, seeking some advise to how to resolve issue with permission/authentication when doing an npm install if the packages comes from a different organization. Here are the contexts:
FROM ORG 1
{"actions":"write","administration":"read","attestations":"read","contents":"write","environments":"read","metadata":"read","packages":"write","secrets":"read"}
FROM ORG 2 [This is where the npm install should be performed]
Upon triggering the workflow, its gets us to this error:
QUESTIONS:
So not sure this time if github supports similar strategy? Or you guys have done it before? Would you mind sharing your thought?
Is there something that needs to be done inside ORG 2's settings?
NOTE: We are leaning away from using PAT.
Beta Was this translation helpful? Give feedback.
All reactions