Improve error logging in Lambda filesystem creation

[Copilot]

Summary

• Modified filesystem creation error handling to log full API response only when error extraction fails

Changes

• Moved full response logging inside the error extraction fallback branch
• Added explicit message when error extraction fails: "could not extract error message. Full response:"
• When error message is successfully extracted from .error, .errors[0].message, or .message, only that message is displayed

Before:

if [ -n "$err_msg" ] && [ "$err_msg" != "null" ]; then
  echo "Filesystem creation failed: $err_msg"
else
  echo "Filesystem creation failed; raw response:"
fi
echo "$fs_resp" | jq . || echo "$fs_resp"  # Always logged

After:

if [ -n "$err_msg" ] && [ "$err_msg" != "null" ]; then
  echo "Filesystem creation failed: $err_msg"
else
  echo "Filesystem creation failed; could not extract error message. Full response:"
  echo "$fs_resp" | jq . || echo "$fs_resp"  # Only logged when extraction fails
fi

Testing

• Not run (reason: workflow YAML change only; validated logic with shell script testing all error extraction paths)

Review focus

• Error handling logic in "Create or select filesystem" step (lines 100-106)

Rollout / Notes

• No runtime impact; improves debugging for unexpected Lambda API error formats

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.