-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: converge on go-jose #1297
Conversation
A single node development cluster (infra-pr-1297) was allocated in production infra for this PR. CI will attempt to deploy 🔌 You can connect to this cluster with:
🛠️ And pull infractl from the deployed dev infra-server with:
🚲 You can then use the dev infra instance e.g.:
Further Development☕ If you make changes, you can commit and push and CI will take care of updating the development cluster. 🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:
LogsLogs for the development infra depending on your @redhat.com authuser: Or:
|
d0917d2
to
d7014d3
Compare
IMO if you can connect to the cluster created in this PR (if it expired, re-run the GH workflows), port-forward and login, see a token on https:/localhost:8443/downloads and your initials in the top-right corner, the auth should work. |
I am testing the dev server, and I found it seems ok until I run
Anyone know why this may be? Otherwise, I can see my auth token (different from my prod one) |
No, but it works for me™. i/o error could be because the curl or jq are failing. If you want to debug this, check if you can see any error from curl or jq. |
Since I ran into issues locally but Tom didn't, I'd like to get at least one more reviewer to take a look and try testing this, if possible. Thank! |
Also, when I tested it, I noticed the token differed from my prod token, so I think when/if this is merged, we'll have to inform everyone they may need to update their tokens locally |
The token on the |
works for me also. |
github.com/dgrijalva/jwt-go
is old and archived in favor ofgithub.com/golang-jwt/jwt
gopkg.in/square/go-jose.v2
is old and archived in favor ofgithub.com/go-jose/go-jose
Honestly wasn't sure which one to pick, so I opted for
go-jose
because it seemed like it had the nicer interface. The stackrox/stackrox repo also uses both, but mostlygo-jose
so that helps with this decision, too.If anyone knows a good way to test this, please let me know