Release Notes - Version 5.0

5.0.1 (2025-01-28)

  • Set client version to 5.2.1.3665

  • Changed $round() calls to be compatible with yvva 1.6 (WEBCLIENT-479).

  • Certain strings in the Web UI were not being displayed in the correct language (WEBCLIENT-477).

  • If a user has no Web Portal (i.e. no Web Portal is specified by the Provider of the user), then the user will now receive an appropriate error message (WEBCLIENT-466).

  • When an Agent container is swapped to cloud storage (see EnableSwapping), the entire installation is now compressed and archived before upload. This ensures that all changes are synchronised, even if this was not completed before backup (WEBCLIENT-471).

    The TempArchivePath setting which specifies a directory to be used to create and unpack archives when using container swapping.

Automatic TeamDrive Agent Update

The Web Portal is now able to update the TeamDrive Agent automatically, without a complete upgrade of the Web Portal software (WEBCLIENT-449).

Update information is downloaded from the URL stored in the AgentUpdateInfoURL setting. The default is: https://agentrelease.teamdrive.net/wpagentrelease.json.

The contents of the wpagentrelease.json file is as follows:

{
      "agent-version" : {
    "<web-portal-version>" : "<agent-version>",
    "<web-portal-version>" : "<agent-version>",
    "<web-portal-version>" : "<agent-version>",
    ...
  }
}

With this format you can specify which version of the TeamDrive Agent is the current version for a particular Web Portal version. If the Web Portal does not find its version in the file, then the next lowest version is applied. However, a version older than the default value of RequiredAgentVersion will never be installed. This is the value of CURRENT_AGENT_VERSION which is hard-coded with the release of a Web Portal version.

A new auto-task: “Check For Updates”, downloads the wpagentrelease.json file and updates the RequiredAgentVersion setting accordingly.

To perform the actual upgrade automatically, the yvva function auto_update_agent must be executed as follows:

yvva --call=auto_update_agent --config-file="/etc/yvva.conf"

The command must be executed with root privileges.

The auto_update_agent function checks and automatically installs the TeamDrive Agent version as specified by the RequiredAgentVersion setting.

However, auto_update_agent only performs this operation if the following two conditions are not met:

  1. The setting AutoUpdateAgent must be set to True, and
  2. the function is called between 2:00 and 4:00 AM.

If not, then auto_update_agent does nothing. So auto_update_agent can be called regularly (once every hour for example) and it will only do an update if automatic upgrade is enabled, and it is early in the morning.

Note that the setting RequiredAgentVersion was previously named MinimumAgentVersion. In addition, ContainerImage has been changed to CurrentAgent. Both settings are now read-only.

The Web Portal will only upgrade the Agent version automatically. If the version specified in the wpagentrelease.json file is lower than the current Agent version then it will be ignored. It is possible to force a downgrade by prefixing the version number of the Agent in the wpagentrelease.json file with ”!”.

Note that containers cannot be downgraded, and will may cease to function if they were started with a older Agent version then before. Such containers must be deleted manually or they will remain unusable until an Agent with a later version is installed.

During upgrade, all other auto-tasks will be disabled. Messages to this affect may appear in the log file as a warning. If upgrade is started and an auto-task is running, then the update process will wait for up to 40 minutes for the task to complete. If the task does not complete in time, upgrade will be aborted and retried in 24 hours.

Setting BuildBinaryName is deprecated and has been removed.

5.0.0 (2024-08-09)

  • First release for CentOS 9. Version number 5 for all server products (TeamDrive Registration Server, TeamDrive Host Server and TeamDrive Web Portal) only stands for the common CentOS 9 release. The actual functionality of the Web Portal is based on the last release 3.1.3 and only includes small changes (see below) and the current client version (see below).
  • HMAC-SHA1 authentication can now be selected for accessing the Registration Server API (WEBCLIENT-463).
  • When using External Authentication there some cases where the login name (usually an email address) that was entered in TeamDrive was not always pre-filled in the External Authentication login page. In addition, if the login name is not an email address, then the field will not be set to read-only.
  • If AllowedProviders is not set then the redirect to the appropriate Web Portal of the user was not always working correctly (WEBCLIENT-465).
  • Set client version to 5.2.0.3615
  • Admin Console: Added a “Restart” button to the details page (WEBCLIENT-469).