internal

check if the lakeFS installation is already set up

Changed on
get/setup_lakefs

Request

  • Base URL
    /api/v1 (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /api/v1/setup_lakefs
  • Auth
    none required

Response

lakeFS setup state

state'initialized' | 'not_initialized'
comm_prefs_missingboolean

true if the comm prefs are missing.

Changes

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • warning

      added the new internal enum value to the / response property for the response status

    • info

      added the optional property / to the response with the status