# Get module version lifecycle status

Compute the lifecycle tier and enforcement action for a specific module version

Endpoint: GET /iacm/api/modules/{id}/lifecycle/versions/{version}
Version: 1.0
Security: x-api-key

## Query parameters:

  - `scope_org` (string)
    Org scope of the module
    Example: "Eligendi illo deserunt quod."

  - `scope_project` (string)
    Project scope of the module
    Example: "Voluptatibus exercitationem ut."

## Path parameters:

  - `id` (string, required)
    Module ID
    Example: "Doloremque earum et est voluptates officia ipsam."

  - `version` (string, required)
    Version to look up
    Example: "Officiis voluptatem molestias aut eligendi ea."

## Header parameters:

  - `Harness-Account` (string, required)
    Account name
    Example: "Numquam quia est."

## Response 200 fields (application/json):

  - `action` (string, required)
    Enforcement action derived from the tier's rule action
    Enum: "no_action", "warn", "fail"

  - `minimum_supported_version` (string)
    The lowest-numbered version currently in the supported tier
    Example: "Voluptatem consequatur quia sunt earum architecto."

  - `tier` (string, required)
    Lifecycle tier: supported, warning, or deprecated
    Enum: "supported", "warning", "deprecated"

## Response 400 fields (application/vnd.goa.error):

  - `fault` (boolean, required)
    Is the error a server-side fault?
    Example: true

  - `id` (string, required)
    ID is a unique identifier for this particular occurrence of the problem.
    Example: "123abc"

  - `message` (string, required)
    Message is a human-readable explanation specific to this occurrence of the problem.
    Example: "parameter 'p' must be an integer"

  - `name` (string, required)
    Name is the name of this class of errors.
    Example: "bad_request"

  - `temporary` (boolean, required)
    Is the error temporary?
    Example: true

  - `timeout` (boolean, required)
    Is the error a timeout?