In preparation for future Spin 1.5 CLI

[tpmccallum]

Signed-off-by: tpmccallum tim.mccallum@fermyon.com

This PR just parks some of the work that Mung did on 1.5 tabs in code blocks; a PR with blank 1.5 code blocks in preparation for the inevitable Spin 1.5 release.

Content must go through a pre-merge checklist.

Pre-Merge Content Checklist

This documentation has been checked to ensure that:

• The title, template, and date` are all set
• Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
• File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
• Has passed bart check
• Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
• Headings are using Title Case
• Code blocks have the programming language set to properly highlight syntax and the proper copy directive
• Have tested with npm run test and resolved all errors
• Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

[github-actions]

🚀 preview deployed successfully to Fermyon Cloud and available at https://fermyon-developer-pr-765-rrso7lpj.fermyon.app

[tpmccallum]

Keep an eye out for possible updates at
spin cloud link
spin plugins install

[tpmccallum]

Please add any additional tasks/suggestions to the following list:

• add 1.5 and plugins changes (cloud app, list and delete etc.) see cl
• Cross-reference 1.5.0
• cloud plugin 0.2.0 is now out, so the new spin cloud apps subcommands are ready to add.
• change Serverless AI documentation from canary to latest (if Serverless AI is fully integrated into the 1.5 release)
• if there are no new Spin CLI subcommands in version 1.5, then (instead of adding yet another tab) perhaps consider resetting the code block tabs to just having 1.5 (and not past versions 1.0, 1.1, 1.2, 1.3, 1.4 ). These will inevitable continue to grow i.e. 1.6, 1.7 and so on. Perhaps a good opportunity to reset.
• SQLite support now in TinyGo -> Add TinyGo SQLite to the API guide #883
• JS/TS example updates per forthcoming js2wasm plugin release? cc @karthik2804
• Document "return null if key does not exist for Kv.getJson” Re: Spin JS SDK
• New version of js2wasm v0.6.0 is out
• Double check Large Language Model (LLM) Support in Spin
• allow outbound http to components in same app by default - only supported in Spin and not supported in Cloud but will be soon
• the install script gives an error message (for users going from canary back to latest):

Error: Newer version 0.6.0post.1693903439 of plugin 'js2wasm' is already installed. To downgrade to version 0.6.0, run `spin plugins upgrade` with the `--downgrade` flag.

• Probably better to just instruct the user on delete canary rather than how to downgrade plugins so the installer can work i.e. spin plugins upgrade --downgrade js2wasm. If a user tries to do the latter then end up with this issue

[vdice]

@tpmccallum cloud plugin 0.2.0 is now out, so the new spin cloud apps subcommands are ready to add.

[vdice]

Spin v1.5.0 is now out, as well as js2wasm v0.6.0

[tpmccallum]

Thanks @vdice
That is super helpful, I will get onto that asap.

[mikkelhegn]

LGTM - with two fixes.

[kate-goldenring]

Just one nit. Thanks Tim!

[itowlson]

I can't get GitHub to make this a suggestion because of embedded backticks, but here is a cough suggestion. Just aiming to clarify that self is not only in allowed_http_hosts and to build out a bit more info about the behaviour.

---

In an HTTP component, you can use the special host self to make HTTP requests within the current Spin application. For example, if you make an outbound HTTP request to http://self/api/customers/, Spin replaces self with whatever host the application is running on. It also replaces the URL scheme (http or https) with the scheme of the current HTTP request. For example, if the application is running in the cloud, Spin changes http://self/api to https://.../api.

Using self means that the application doesn't need to know the URL where it's deployed, or whether it's running locally versus in the cloud.

This doesn't work in Redis components because Spin uses the incoming HTTP request to determine the current host.

You must still grant permission by including self in allowed_http_hosts:

allowed_http_hosts = ["self"]

[tpmccallum]

Thanks Ivan, this is REALLY helpful.

[tpmccallum]

Added in the new push.