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
There is currently no clear way of how pushing a signature to a specific organization/prefix would work, and logins with login -o have no effect on where the signature is being pushed to.
Versions used:
pojntfx@fedora:~$ go version
go version go1.21.1 linux/amd64
pojntfx@fedora:~$ scale version
scale version v0.1.7-dev12 (build date: Sat Oct 21 00:42:52 UTC 2023 git commit: 676f8de0feb1371469be159c3de896848f4e61e5 go version: go1.21.3 build platform: linux/amd64)
Steps to reproduce:
$ scale login -o atmosfeed
Confirmation Code: XHEHUTAA
Opening browser to https://scale.sh/device-auth?code=XHEHUTAA&organization=atmosfeed
If something goes wrong, copy and paste this URL into your browser: https://scale.sh/device-auth?code=XHEHUTAA&organization=atmosfeed
Logged in as [email protected] (using organization felicitaspojtinger)
$ scale registry signature push local/classifier:latest
Pushed signature felicitaspojtinger/classifier:latest to the Scale Registry
The following packages are now publicly available:
Golang (Guest): go.scale.sh/v1/felicitaspojtinger/classifier/latest/guest
Golang (Host): go.scale.sh/v1/felicitaspojtinger/classifier/latest/host
Rust (Guest): felicitaspojtinger_classifier_latest_guest
I would have expected the signature classifier to have been pushed to atmosfeed/classifier instead of felicitaspojtinger/classifier.
It is also not possible to create a signature with an org in the name locally, adding to the confusion:
$ scale signature generate atmosfeed/classifier:latest -d ./pkg/signatures/classifier
Error: invalid name 'atmosfeed/classifier', names can only include letters, numbers, periods (`.`), and dashes (`-`)
The text was updated successfully, but these errors were encountered:
There is currently no clear way of how pushing a signature to a specific organization/prefix would work, and logins with
login -o
have no effect on where the signature is being pushed to.Versions used:
Steps to reproduce:
I would have expected the signature
classifier
to have been pushed toatmosfeed/classifier
instead offelicitaspojtinger/classifier
.It is also not possible to create a signature with an org in the name locally, adding to the confusion:
The text was updated successfully, but these errors were encountered: