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
Replace generateApiKey with generateProvisioningKey #410
Conversation
Change-Type: major
60b2a8d
to
c67d8d0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other that the typo, LGTM
resin.models.application.getApiKey(@application.app_name).then (apiKey) -> | ||
m.chai.expect(_.isString(apiKey)).to.be.true | ||
m.chai.expect(apiKey).to.have.length(32) | ||
it 'should be able to generate an provisioning key by name', -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "a provisioning key" better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn, good spot. Fixed.
…ateProvisioningKey We now no longer allow generating app wide keys. Generate a provisioning key to register new devices, and look at JWTs or user API keys (coming soon) for other uses. Change-Type: major
c67d8d0
to
3bafe78
Compare
I'm going to wait for @Page- to confirm before I merge this, just because I'm not confident my understanding of the provisioning key work is totally correct. |
Replace generateApiKey with generateProvisioningKey
Replace generateApiKey with generateProvisioningKey
This is already deprecated in the API, and we really shouldn't be using or exposing it here. This replaces it with provisioning keys, which are the modern alternative.
This is another fun breaking change, so another inclusion for big lovely v7.