Fix: remove $context.status from websocket access log format

[sammarks]

What did you implement

It looks like AWS may have recently introduced a change where $context.status is invalid on API Gateway WebSocket APIs (or at least now they're enforcing invalid tokens).

The following context variables are not supported: [$context.status] (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: a37f886a-d719-485d-9593-fe2b14182df7)

This change simply removes the offending token from the WebSocket log format so WebSocket APIs will deploy properly.

How can we verify it

Create a WebSocket-based service.

service: websocket-test
provider:
  logs:
    websocket: true
functions:
  websocket:
    handler: src/websocket
    events:
      - websocket: $default

Todos

Useful Scripts

• npm run test-ci --> Run all validation checks on proposed changes
• npm run lint-updated --> Lint all the updated files
• npm run lint:fix --> Automatically fix lint problems (if possible)
• npm run prettier-check-updated --> Check if updated files adhere to Prettier config
• npm run prettify-updated --> Prettify all the updated files

• Write and run all tests
• Write documentation
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES
Is it a breaking change?: NO

[codecov-io]

Codecov Report

Merging #7014 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7014   +/-   ##
=======================================
  Coverage   88.48%   88.48%           
=======================================
  Files         229      229           
  Lines        8416     8416           
=======================================
  Hits         7447     7447           
  Misses        969      969

Impacted Files	Coverage Δ
...aws/package/compile/events/websockets/lib/stage.js	100% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d0c6c8d...d1537f7. Read the comment docs.

[medikoo]

Thank you @sammarks !

[leclercb]

Is there any workaround in the meantime ?
This bug is currently preventing any deployment of application using websockets.
I tried with websocket logs to false, the problem is the same.
Thanks

[sammarks]

@leclercb I’ve just updated my package.json to point to my fork directly until we get a new release with the fix included. Or since it’s merged into master now you can just update yours to point to the master branch instead of a specific version.

[Gr8z]

Is this gonna be released soon? This this blocking all deployments, and since we use Github Actions, we can't change the package.json

[henhal]

Gah, found this only now. This fixes #7038. When will this be released?

@Gr8z For a temp workaround look at #7038 !

[medikoo]

Sorry for delay. It'll be released first thing tomorrow CET morning.