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
The issue is that the key authentication does not have permission to describe the key and get the tags, and since we don't get any from the cli args, it logs that there's no tags.
Options I see:
Add permissions to provisioner keys to get tag information
Remove log line altogether if it's not critical information
Checked with @f0ssel and the best approach seems to be to add a new endpoint authorized by a valid provisioner key and returns the detailed of the provisioner key used to authenticate. Kind of similar to /api/v2/users/me.
This will also allow the provisioner to validate the key before opening a websocket and connecting to coderd.
Right now we log a line with the tags we are using for the provisioner, and when using
--key
it says it's "untagged" which isn't true.The issue is that the key authentication does not have permission to describe the key and get the tags, and since we don't get any from the cli args, it logs that there's no tags.
Options I see:
Spun out from #15047
The text was updated successfully, but these errors were encountered: