Unclear output from action.

[PaulRudin]

I have an action that invokes as follows:

      - name: Deploy Fastly Compute
        uses: fastly/compute-actions@v11
        with:
          token: ${{ env.FASTLY_API_TOKEN }}
          service_id: ${{ env.FASTLY_SERVICE_ID }}
          project_directory: fastly

this runs fine,

but the output from the action is:

Run fastly/compute-actions@v11
/opt/hostedtoolcache/fastly/11.4.0/x64/fastly version
Fastly CLI version v11.4.0 (f42c8033)
Built with go version go1.24.4 linux/amd64 (2025-08-12)
/opt/hostedtoolcache/fastly/11.4.0/x64/fastly compute build --non-interactive
IMPORTANT: The Fastly CLI is configured to collect data related to Wasm builds (e.g. compilation times, resource usage,
and other non-identifying data). To learn more about what data is being collected, why, and how to disable it:
https://www.fastly.com/documentation/reference/cli

| Verifying fastly.toml...
✓ Verifying fastly.toml
| Fetching latest wasm-tools release...
/ Fetching latest wasm-tools release...
- Fetching latest wasm-tools release...
✓ Fetching latest wasm-tools release
| Identifying package name...
✓ Identifying package name
| Identifying toolchain...
✓ Identifying toolchain
| Running [scripts.build]...
/ Running [scripts.build]...
- Running [scripts.build]...
✓ Running [scripts.build]
| Creating package archive...
/ Creating package archive...
- Creating package archive...
✓ Creating package archive

SUCCESS: Built package (pkg/games-compute-service.tar.gz)

So whilst it mentions building it doesn't say anything about deploying. Checking the relevant service I can see that the package was deployed, but it would be nice if the action's output printed something to that effect.

[kpfleming]

I just ran into this as well - the deploy actually happens in the Post phase, not during the main phase of the job. This is surprising and I'm not sure there's a reason it needs to be this way - when the deploy fails for some reason the step labeled "Deploy Fastly Compute" in the job log is green, even though the deploy failed.

@kailan Is there a specific reason why the deploy Action works this way, with the build and deploy commands run in separate phases of the job?

[kailan]

I just ran into this as well - the deploy actually happens in the Post phase, not during the main phase of the job. This is surprising and I'm not sure there's a reason it needs to be this way - when the deploy fails for some reason the step labeled "Deploy Fastly Compute" in the job log is green, even though the deploy failed.

@kailan Is there a specific reason why the deploy Action works this way, with the build and deploy commands run in separate phases of the job?

I believe it was purely a misunderstanding when this was originally built. The action should certainly be updated to build and deploy in the main phase.