#Error with github action to upload a module

1 messages · Page 1 of 1 (latest)

frigid geyser
#

Hey all on my first try to cut a release (https://github.com/IanWhalen/led/actions/runs/6210301193/job/16858358056) I'm getting the following error on this action:

Error: Unable to connect to "https://app.viam.com:443" using the provided api key: rpc error: code = PermissionDenied desc = API key authentication requires passing the UUID key ID in as the entity

which I'm assuming just has something to do with how I've maybe set my org-id in my action? https://github.com/IanWhalen/led/blob/c6f0c0abbf0a52e1ed9a7695f3e49303b56c3812/.github/workflows/main.yml
But I can't figure out what the fix is.

shrewd crane
frigid geyser
#

oh yeah that's good to compare it to. I don't think I ever had to provide an org id when doing it manually?

ian@dog:~/led $ viam module upload --version 0.1.0 --platform linux/arm64 module.tar.gz 
uploading... 100% (1506/1506 bytes)
version successfully uploaded! you can view your changes online here: https://app.viam.com/module/ianwhalen/neopixel
shrewd crane
#

I am currently only finding examples that are public modules (probably makes sense) and they don't use the org-id because they are public

#

but still scanning

#

but can you try viam module upload --version 0.1.1 --org-id 'a3a451d6-5564-4954-b0aa-e57d5f16cab7' --platform linux/arm64 module.tar.gz

#

I don't don't if you need the quotes tbf - possibly without

frigid geyser
#

Ok yeah I guess I can also just remove that line since it’s a public module? But then continue trying to figure out what the error is in case someone else hits it

shrewd crane
#

yeah - so I just noticed that your meta.json has "visibility": "public"

#

it seems to still assume I want to upload this to a public namespace though

#

ah and if you run viam module update - it says you can't now set it to private because it's already public. so you'd have to create a new module to test it (which I'll get started doing)

shrewd crane