Update wasm functions docs for v0.4 plugin

Signed-off-by: Caleb Schoepp <[email protected]>

Author: calebschoepp

content/wasm-functions/app-linking.md

@@ -0,0 +1,80 @@
+title = "Link Applications"
+template = "functions_main"
+date = "2025-01-16T00:22:56Z"
+enable_shortcodes = true
+
+---
+- [Upgrade Your Application](#upgrade-your-application)
+  - [Specifying Variables](#specifying-variables)
+- [Next Steps](#next-steps)
+TODO
+
+Your local workspace can be linked to an application running in _Fermyon Wasm Functions_. This is a convenience so that you don't always have to specify the `--app-name` when running commands.
+
+{{ details "What is a workspace?" "A workspace is a directory on your local machine that contains the Spin application code and manifest file. It is where you develop and test your application before deploying it to _Fermyon Wasm Functions_. Any child directory of where the Spin manifest is located is also considered part of the workspace." }}
+
+## Inspecting Your Workspace
+
+You can see information about the current workspace by navigating to the directory where your Spin application is located and running the following command:
+
+<!-- @selectiveCpy -->
+
+```console
+$ spin aka info
+```
+
+Among other things this will tell if your workspace is linked to an application on _Fermyon Wasm Functions_ and if so which one.
+
+<!-- @nocpy -->
+
+```console
+Auth Info
+  Accounts: your-account
+Workspace Info
+  Root dir: /Users/user/src/hello-spin
+  Linked app: hello-spin
+```
+
+If you ran `spin aka deploy` for the first time it will have automatically linked your workspace to the application you just deployed.
+
+## Linking Your Workspace
+
+If your workspace is not linked to an application, you can link it by running the following command:
+
+<!-- @selectiveCpy -->
+
+```console
+$ spin aka link
+```
+
+This command will prompt you to select an application to link to. You can also specify the application name directly:
+
+<!-- @selectiveCpy -->
+
+```console
+$ spin aka link --app-name <app-name>
+```
+
+This will link your workspace to the specified application. You can verify that the workspace is linked by running the `spin aka info` command again.
+
+## Running Commands
+
+Now anytime you run a command in this workspace it will automatically assume that you want to run it against the linked application. For example if you run `spin aka deploy` it will upgrade that application. If you run `spin aka logs` it will show the logs for that application and so on.
+
+## Unlinking Your Workspace
+
+If you wish to unlink your workspace from the currently linked application, you can do so by running the following command:
+
+<!-- @selectiveCpy -->
+
+```console
+$ spin aka unlink
+```
+
+You can run `spin aka info` again to verify that the workspace is no longer linked to an application.
+
+{{ details "Note" "Unlinking your workspace does not delete the application on _Fermyon Wasm Functions_. It simply removes the link between your local workspace and the application." }}
+
+## Next Steps
+
+- [List and Inspect Applications](list-and-inspect)

content/wasm-functions/delete.md

@@ -12,15 +12,15 @@ It’s easy to delete an Spin application from _Fermyon Wasm Functions_. This ca
 
 ## Find the Application You Want to Delete
 
-First, you may want to find the application you want to delete, you could use the `spin aka apps list` command to retrieve a list of all Spin applications deployed to your _Fermyon Wasm Functions_ account:
+First, you may want to find the application you want to delete, you could use the `spin aka app list` command to retrieve a list of all Spin applications deployed to your _Fermyon Wasm Functions_ account:
 
 <!-- @selectiveCpy -->
 
 ```console
-$ spin aka apps list
+$ spin aka app list
 ```
 
-<!-- @nocpy --> 
+<!-- @nocpy -->
 
 ```console
 hello-fermyon-wasm-functions
@@ -30,15 +30,15 @@ query-external-database
 
 ## Delete Your Application
 
-Use the `spin aka apps delete` command to delete a particular Spin application from your _Fermyon Wasm Functions_ account:
+Use the `spin aka app delete` command to delete a particular Spin application from your _Fermyon Wasm Functions_ account:
 
 <!-- @selectiveCpy -->
 
 ```console
-$ spin aka apps delete --name validate-jwt-tokens
+$ spin aka app delete --app-name validate-jwt-tokens
 ```
 
-The `spin aka apps` command, will ask you to confirm deleting the application of choice. Once confirmed, the application will be removed from your _Fermyon Wasm Functions_ account.
+The `spin aka app delete` command, will ask you to confirm deleting the application of choice. Once confirmed, the application will be removed from your _Fermyon Wasm Functions_ account.
 
 <!-- @nocpy -->
 
@@ -51,4 +51,4 @@ That’s all about deleting your Spin Application from _Fermyon Wasm Functions_!
 
 ## Next Steps
 
-- Make sure to check the [FAQ and Known Limitations](faq) article
+- Make sure to check the [FAQ and Known Limitations](faq) article

content/wasm-functions/deploy.md

@@ -84,11 +84,15 @@ $ spin aka deploy
 <!-- @nocpy -->
 
 ```console
-App 'myapp' initialized successfully.
-Deploying application to Fermyon Wasm Functions on Akamai..
-Waiting for application to be ready... ready
-
-View application:   https://c8769081-7ae5-4041-a10f-61d344a67da2.aka.fermyon.tech/
+Name of new app: myapp
+Creating new app myapp in account your-account
+Note: If you would instead like to deploy to an existing app, cancel this deploy and link this workspace to the app with `spin aka app link`
+OK to continue? yes
+Workspace linked to app myapp
+Waiting for app to be ready... ready
+
+App Routes:
+- myapp: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 ### Specifying Variables
@@ -115,10 +119,12 @@ $ spin aka deploy --variable compression_level=3
 <!-- @nocpy -->
 
 ```console
-Deploying application to Fermyon Wasm Functions on Akamai..
-Waiting for application to be ready... ready
+Deploying updated version of app my-app in account your-account (version 1 → 2)
+OK to continue? yes
+Waiting for app to be ready... ready
 
-View application:   https://c8769081-7ae5-4041-a10f-61d344a67da2.aka.fermyon.tech/
+App Routes:
+- my-app: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 ---

content/wasm-functions/get-logs.md

@@ -8,20 +8,18 @@ enable_shortcodes = true
 - [Retrieving Logs of Your Application](#retrieving-logs-of-your-application)
 - [Next Steps](#next-steps)
 
-Retrieving logs of your Spin applications at runtime is crucial to understand runtime behavior and for gathering insights. 
+Retrieving logs of your Spin applications at runtime is crucial to understand runtime behavior and for gathering insights.
 
 ## Retrieving Logs of Your Application
 
 Use the `spin aka logs` command, to retrieve logs of your Spin application deployed to _Fermyon Wasm Functions_.
 
-If you invoke the command from within the directory of your Spin application (the directory in which your `spin.toml` file is located), it will - by default - load all logs of the current Spin application.
-
-If the command is invoked outside the application directory, or if you want to receive log messages of a particular Spin application running on _Fermyon Wasm Functions_, you must explicitly specify the name of the application using the `--app` flag:
+By default it will provide logs for the application that your workspace is [linked to](app-linking). If your workspace is not linked to an application, you can specify the application name using the `--app-name` flag.
 
 <!-- @selectiveCpy -->
 
 ```console
-$ spin aka logs --app hello-fermyon-wasm-functions
+$ spin aka logs --app-name hello-fermyon-wasm-functions
 ```
 
 The `spin aka logs` command, will print all log messages to `stdout` as shown here:
@@ -35,8 +33,8 @@ The `spin aka logs` command, will print all log messages to `stdout` as shown he
 2025-01-16 13:32:04 [hello-fermyon-wasm-functions]  2025/01/16 13:31:56 INFO POST https://11077e3b-d632-4df3-921f-f7ebefb9aaca.aka.fermyon.tech/greet: Handled by handle_greet func
 ```
 
-The log messages shown above have been generated using the [`log/slog` package](https://go.dev/blog/slog) by a Spin application written in Go. Technically, everything your Spin application writes to `stdout` and `stderr` will be captured by _Fermyon Wasm Functions_ and made accessible via the `spin aka logs` command. 
+The log messages shown above have been generated using the [`log/slog` package](https://go.dev/blog/slog) by a Spin application written in Go. Technically, everything your Spin application writes to `stdout` and `stderr` will be captured by _Fermyon Wasm Functions_ and made accessible via the `spin aka logs` command.
 
 ## Next Steps
 
-- [Delete an application](delete)
+- [Delete an application](delete)

content/wasm-functions/list-and-inspect.md

@@ -12,12 +12,12 @@ This articles illustrates how to list and inspect Spin applications deployed to
 
 ## List Your Applications
 
-To list all Spin applications deployed to your _Fermyon Wasm Functions_ account, use the `spin aka apps list` command as shown in the following snippet:
+To list all Spin applications deployed to your _Fermyon Wasm Functions_ account, use the `spin aka app list` command as shown in the following snippet:
 
 <!-- @selectiveCpy -->
 
 ```console
-$ spin aka apps list
+$ spin aka app list
 ```
 
 Depending on which apps you have deployed to your _Fermyon Wasm Functions_ account, the actual output will differ from the output shown here.
@@ -30,12 +30,12 @@ validate-jwt-tokens
 query-external-database
 ```
 
-By default, `spin aka apps list` will print the name of each Spin application deployed to your _Fermyon Wasm Functions_ account as plain text. Alternatively, you could add the `--format` flag and change the output format to `JSON`:
+By default, `spin aka app list` will print the name of each Spin application deployed to your _Fermyon Wasm Functions_ account as plain text. Alternatively, you could add the `--format` flag and change the output format to `JSON`:
 
 <!-- @selectiveCpy -->
 
 ```console
-$ spin aka apps list --format json
+$ spin aka app list --format json
 ```
 
 This time, you'll receive the list of Spin applications as `JSON` array:
@@ -61,19 +61,22 @@ query-external-database(b6cc1427-392c-4f96-859d-bb4d0adc216c)
 
 ## Inspecting an Application
 
-Use the `spin aka apps info` command, to gather fundamental information about a Spin application deployed to your _Fermyon Wasm Functions_ account. The command requires the name of the desired application to be passed as an argument to the `--app` flag:
+Use the `spin aka app status` command, to gather fundamental information about a Spin application deployed to your _Fermyon Wasm Functions_ account. The command will provide the status of the application your workspace is [linked to](app-linking). Alternatively, you can specify a specific app with the `--app-name` flag.
 
 <!-- @selectiveCpy -->
 
 ```console
-$ spin aka apps info --name hello-fermyon-wasm-functions
+$ spin aka app status
 ```
 
 <!-- @nocpy -->
 
 ```console
 Name: hello-fermyon-wasm-functions
-URL: https://25a5fd1e-d476-40fd-bc54-6cee0e846540.aka.fermyon.tech/
+ID: ec8a19d8-6d10-4056-bb69-cc864306b489
+URL: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech
+Created at: 2025-05-23 16:11:49 UTC
+Invocations: 229 in the past 7 days
 ```
 
 As you can see, you'll also receive the public origin, which could be used to access the Spin application. Similar to the `spin aka apps list` command, you could add the `--format json` flag to make the command return fundamental information about a particular application as `JSON` object:
@@ -87,11 +90,16 @@ $ spin aka apps info --name hello-fermyon-wasm-functions --format json
 
 ```json
 {
+  "id": "ec8a19d8-6d10-4056-bb69-cc864306b489",
   "name": "hello-fermyon-wasm-functions",
-  "url": "https://25a5fd1e-d476-40fd-bc54-6cee0e846540.aka.fermyon.tech/"
+  "urls": [
+    "https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech"
+  ],
+  "created_at": "2025-05-23 16:11:49 UTC",
+  "invocations": "229 in the past 7 days"
 }
 ```
 
 ## Next Steps
 
-- [Get Application Logs](get-logs)
+- [Get Application Logs](get-logs)

content/wasm-functions/property-manager-integration.md

@@ -69,10 +69,15 @@ The `spin aka deploy` command will generate an output similar to the one shown b
 <!-- @noCpy -->
 
 ```console
-App 'hello-fermyon-wasm-functions' initialized successfully.
-Waiting for application to be ready... ready
-
-View application: https://27383f31-adbe-482f-a859-2ce9aad02c4f.aka.fermyon.tech/
+Name of new app: hello-fermyon-wasm-functions
+Creating new app hello-fermyon-wasm-functions in account your-account
+Note: If you would instead like to deploy to an existing app, cancel this deploy and link this workspace to the app with `spin aka app link`
+OK to continue? yes
+Workspace linked to app hello-fermyon-wasm-functions
+Waiting for app to be ready... ready
+
+App Routes:
+- hello-fermyon-wasm-functions: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 Copy the URL from the output shown in your terminal, we'll need it in a second to configure the Akamai Property.

content/wasm-functions/querying-linode-mysql.md

@@ -488,10 +488,15 @@ The above deploy command will produce similar output to the following:
 <!-- @nocpy -->
 
 ```bash
-App 'linode-mysql' initialized successfully.
-Waiting for application to be ready... ready
-
-View application:   https://8d332abd-5f9e-4943-aaaa-60c219213410.aka.fermyon.tech/
+Name of new app: linode-mysql
+Creating new app linode-mysql in account your-account
+Note: If you would instead like to deploy to an existing app, cancel this deploy and link this workspace to the app with `spin aka app link`
+OK to continue? yes
+Workspace linked to app linode-mysql
+Waiting for app to be ready... ready
+
+App Routes:
+- linode-mysql: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 Finally, you can use `curl` to interact with the application you just deployed to _Fermyon Wasm Functions_. First, let's send a `GET` request to the `/products` endpoint to retrieve a list of all products:

content/wasm-functions/querying-postgresql.md

@@ -440,9 +440,15 @@ The above deploy command will produce similar output to the following:
 <!-- @nocpy -->
 
 ```bash
-Waiting for application to be ready... ready
-Application deployed to https://rust-pg-12345678.aka.fermyon.tech/
-View application: https://rust-pg-12345678.aka.fermyon.tech/
+Name of new app: hello-postgresql
+Creating new app hello-postgresql in account your-account
+Note: If you would instead like to deploy to an existing app, cancel this deploy and link this workspace to the app with `spin aka app link`
+OK to continue? yes
+Workspace linked to app hello-postgresql
+Waiting for app to be ready... ready
+
+App Routes:
+- hello-postgresql: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 Finally, you can use `curl` to interact with the application you just deployed to _Fermyon Wasm Functions_. First, let's send a `GET` request to the `/products` endpoint to retrieve a list of all products:

content/wasm-functions/quickstart.md

@@ -509,7 +509,7 @@ $ spin aka login
 <!-- @nocpy -->
 
 ```console
-Go to https://login.neutrino.fermyon.computer/realms/neutrino/device?user_code=BB-AA
+Go to https://login.infra.fermyon.tech/realms/neutrino/device?user_code=BB-AA
 and follow the prompts.
 
 Don't worry, we'll wait here for you. You got this.
@@ -527,7 +527,7 @@ Finally, let's deploy the application to _Fermyon Wasm Functions_:
 $ spin aka deploy
 ```
 
-The `spin` command will run using the Spin binary in your system path and read the Spin application definition file `spin.toml` in the current (`hello-spin`) directory to know what application to deploy.
+The `spin` command will run using the Spin binary in your system path and read the Spin application definition file `spin.toml` in the current (`hello-spin`) directory to know what application to deploy. It will ask you for a name for the application (defaulting to `hello-spin`) and then it will ask for confirmation that you want to deploy.
 
 {{ details "Learn more" "Deploying a Spin application to _Fermyon Wasm Functions_ includes packaging the application and all the required files, uploading it to an OCI registry, as well as instantiating the application on _Fermyon Wasm Functions_. " }}
 
@@ -538,12 +538,15 @@ This is what a successful Spin application deployment on Fermyon Wasm Functions
 <!-- @nocpy -->
 
 ```console
-Pushing app to the Registry....
-App 'hello-spin' initialized successfully.
-Waiting for application to be ready... ready
-
-Application deployed to https://ac465a57-8d62-443e-a8ed-f50872dd17b7.aka.fermyon.tech/
-View application:   https://ac465a57-8d62-443e-a8ed-f50872dd17b7.aka.fermyon.tech/
+Name of new app: hello-spin
+Creating new app hello-spin in account your-account
+Note: If you would instead like to deploy to an existing app, cancel this deploy and link this workspace to the app with `spin aka app link`
+OK to continue? yes
+Workspace linked to app hello-spin
+Waiting for app to be ready... ready
+
+App Routes:
+- hello-spin: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 You can `CTRL`+Click on the link in the terminal to visit the web application you just deployed.

content/wasm-functions/stream-data-from-linode-object-store.md

@@ -363,10 +363,15 @@ Deployment to _Fermyon Wasm Functions_ will take a couple of seconds, once the d
 <!-- @nocpy -->
 
 ```console
-App 'linode-streaming-app' initialized successfully.
-Waiting for application to be ready... ready
-
-View application:   https://70b79692-1028-4aa5-9395-e311f44d038b.aka.fermyon.tech/
+Name of new app: linode-streaming-app
+Creating new app linode-streaming-app in account your-account
+Note: If you would instead like to deploy to an existing app, cancel this deploy and link this workspace to the app with `spin aka app link`
+OK to continue? yes
+Workspace linked to app linode-streaming-app
+Waiting for app to be ready... ready
+
+App Routes:
+- linode-streaming-app: https://ec8a19d8-6d10-4056-bb69-cc864306b489.aka.fermyon.tech (wildcard)
 ```
 
 ## Conclusion