feat: sdk

[gentlementlegen]

Resolves #15

[github-actions]

Unused dependencies (2)

Filename	dependencies
package.json	@octokit/rest @octokit/webhooks

[gentlementlegen]

/query @gentlementlegen

[ubiquity-os]

Property	Value
Wallet	0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED

[gentlementlegen]

/query @gentlementlegen

[ubiquity-os]

Property	Value
Wallet	0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED

[gentlementlegen]

@whilefoo I had a question. Now that we have the SDK, I included it in this plugin. Everything seems fine but now every time it runs the verification fails. Shall this plugin have something set in the environment (although I see there is already a public key included) or is it something missing on the kernel side?

PS: I guess it will void this pull request: #4

[gentlementlegen]

@whilefoo thank you I missed that step, I got it to work with my own workers.

QA: Meniole#4 (comment)

That raises a few questions on my side:

First, the SDK will probably have to be changed because for the environment it reads process.env, which exists within Cloudflare but is not populated with the Env set by wrangler, which instead passes it as an argument of fetch. That forced me to wrap the creation of the kernel like so, and the environment validation cannot be run by the SDK.

Second, what is exactly the purpose of the key validation? The kernel configuration can only be changed by admins so it will call only the plugins we allow. And on the plugin side, since we embed the public key, anyone who would fork the plugin could have potentially this fork running if somehow they get to set the URL in the configuration? Maybe I miss something but I can't see what this protection is for. I just understood that it is the other way around, to avoid having a kernel calling any plugin freely.

[gentlementlegen]

/query @gentlementlegen

[ubiquity-os]

Property	Value
Wallet	0x0fC1b909ba9265A846b82CF4CE352fc3e7EeB2ED

[whilefoo]

First, the SDK will probably have to be changed because for the environment it reads process.env, which exists within Cloudflare but is not populated with the Env set by wrangler, which instead passes it as an argument of fetch.

The Hono server automatically reads the env from Cloudflare fetch or from process.env if it's run in Node.
I didn't even notice that I'm validating the env from the process.env instead of from Hono context.

[gentlementlegen]

@whilefoo Updated and upgraded the kernel, tried to simplify the fetch but I don't think I can just export default because I need the env.KERNEL_PUBLIC_KEY to be passed in the options of createPlugin.