Versions Compared

Version Old Version 103 New Version 104
Changes made by

Lakshmi Manda

John Brinckwirth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
minLevel1
maxLevel1
include
outlinefalse
indent
exclude
typeflat
separatorbrackets
class
printablefalse

...

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFEBE6

Breaking Change

With the new support for LDAP authentication to HashiCorp Vaults, the Snaplex node configuration file secrets-config.json requires a new key, auth_method, with a value approle or ldap.

Action needed:

You must update each of your existing Snaplex node configuration files to include this key-value pair: "auth_method": "approle", as prescribed in the Step 1a-Approle, for the approle-based authentication to succeed.

...

  • The Runtime Archive does not display content.

  • The API response for Snaplex Configuration REST API gives the incorrect Snaplex version to download. Instead of the recommended Snaplex version, the response gets the latest version.
    Workaround: Use the Snaplex dialog Downloads tab for the recommended version.

  • In GitHub, you cannot create a branch doing a Git checkout from the repository at the Project Space level.

  • The Git status Updated does not work at the Project space level for all Git repos.

  • In GitHub, when a root folder is already untracked in a Project Space after doing the checkout, the root (1) folder is not created.

  • For GitLab integration, when updating the Git assets with the status Tracked Modified locally and remotely, a conflict error message displays.

  • For GitLab integration, while creating a Project from a Git checkout, an error message displays.

  • For GitLab integration, doing a Git Repository Checkout with Hard Reset results in an internal server error.

  • If a self-managed GitLab server does not have GitLab as part of the hostname, Status, Pull, Commit, Create Branch, and Create Tag commands fail.

...