實作容器映像的 SnapStart 掛鉤

執行快照前掛鉤並觸發快照程序：作為函數初始化程式碼的最後一個步驟，視需要執行快照前掛鉤並觸發快照程序。只有在啟用 SnapStart 時才執行這些步驟，方法是檢查AWS_LAMBDA_INITIALIZATION_TYPE環境變數的值是否設定為 snap-start。執行您已註冊的快照前掛鉤，然後呼叫 GET /runtime/restore/next 來觸發快照程序。如果擷取前勾點擲回或傳回錯誤，執行時間會將錯誤發佈到/runtime/init/error端點。請參閱以下虛擬程式碼範例：

# After all initialization code has finished:

    READ initialization_type FROM environment variable "AWS_LAMBDA_INITIALIZATION_TYPE"

    IF initialization_type IS "snap-start" THEN

        TRY
            EXECUTE registered before-snapshot hooks
        ON ERROR
            POST error to /runtime/init/error
                SET header  Lambda-Runtime-Function-Error-Type  TO  <Category>.<Reason>
                SET body    TO  { errorMessage, errorType, stackTrace }
            EXIT process with non-zero code

        # Signal readiness for snapshot
        SEND GET request to /runtime/restore/next
        # The request blocks until Lambda restores the execution environment from the snapshot, then returns HTTP 200.

    END IF

執行還原後掛鉤，然後輸入叫用迴圈。當 GET /runtime/restore/next傳回 200 時，您的執行時間必須執行任何已註冊的還原後掛鉤，才能繼續叫用迴圈。如果還原後掛鉤失敗，請向 報告錯誤/runtime/restore/error。還原後掛鉤完成後，請呼叫 來輸入標準叫用迴圈GET /runtime/invocation/next。從此時開始，行為與不使用 SnapStart 的函數相同。請參閱以下虛擬程式碼範例：

# After the snapshot has been restored
# (i.e., GET /runtime/restore/next has returned HTTP 200):

    TRY
        EXECUTE registered after-restore hooks
    ON ERROR
        POST error to /runtime/restore/error
            SET header  Lambda-Runtime-Function-Error-Type  TO  <Category>.<Reason>
            SET body    TO  { errorMessage, errorType, stackTrace }

# Proceed to the invoke loop