Skip to main content

3.7.0 to 3.7.1

This document describes the upgrade instructions from 3.7.0 to 3.7.1.

Patch release​

This is a patch release to fix known issues in version 3.7.0. If you are using 3.7.0, you should upgrade to this version or later to avoid potential issues with sequence editor workspaces and actions.

Workspace Permissions Changes​

Aerie version 3.6.0 introduced a significant change to the way sequence editor workspaces are managed. An unintended consequence of this change made it so that only users with the aerie_admin role could modify files in the workspace. This version changes permissions to allow users with the aerie_user role to edit files in workspaces. Currently, all users with this role can edit all files in all workspaces. An upcoming release will allow users to restrict a workspace's permissions to a list of specified collaborators only.

Configuration changes​

hasura container config​

If your deployment's docker-compose file defines the AERIE_DATABASE_URL environment variable in the hasura section, it should be updated to the following value:

  hasura:
    environment:
      AERIE_DATABASE_URL: "postgres://${AERIE_USERNAME}:${AERIE_PASSWORD}@postgres:5432/aerie?options=-c%20search_path%3Dutil_functions%2Chasura%2Cpermissions%2Ctags%2Cmerlin%2Cscheduler%2Csequencing%2Cactions%2Cui%2Cpublic"
      # ...

This change is required in order to support custom file extension mappings in the seqeunce editor.

aerie-ui container config​

Aerie 3.7.0 added the ability to define secret-type parameters on Actions, and pass them to the Action as "transient secrets" at runtime, bypassing the database entirely to ensure no secrets are saved. In order to use this feature:

  1. The UI (browser) must be able to make requests to the action-server directly. This means that action-server's port (27186) must be accessible. If your Aerie instance is running behind a proxy, load-balancer or firewall, you will need to configure it to allow connections on this port, or serve it on a separate domain/subdomain.
  2. You must provide the environment variable PUBLIC_ACTION_CLIENT_URL to the aerie-ui container so the UI knows where to reach the action service. In your docker compose file, add or update the following line in the environment section within aerie_ui. (YOUR_HOST_NAME is the host name/URL of your deployment, or localhost for local deployment)
  aerie_ui:
    environment:
      PUBLIC_ACTION_CLIENT_URL: http://YOUR_HOST_NAME:27186

See this docker-compose file for an example.

tables.yaml file​

If you are managing custom Hasura metadata .yaml files for your deployment (instead of using the ones included in our Deployment.zip), you will need to make sure the file hasura/metadata/databases/tables/tables.yaml contains the following include statement:

- "!include ui/file_extension_content_type.yaml"

See this file for an example.