See also the fleetcommand-agent Release Notes.
-
You can now define content security policies for published Domino web apps. By default, any direct request made from the front-end of a web app is blocked unless it’s whitelisted by your Domino administrator. See Content security policies.
-
Fixed an issue that set the incorrect role for new users on an upgraded deployment.
-
Fixed an issue that prevented roles from being assigned to users when performing a Domino upgrade.
-
Fixed an issue that prevented workspaces from launching.
-
Fixed an issue that prevented a model’s name from being updated when using the Python wrapper for the Domino API.
-
There is an issue with the execution service account token for Domino installations on OpenShift.
-
Domino CLI on BigSur MacOS has issues with deleted files synchronization.
-
When runs are initiated through the API or Save and Run button in the Files tab, the EDV does not mount.
-
An external dependency was removed on 7/24/21, causing build failures for DAD-related environments.
-
Every Domino execution causes the Domino CLI to print log4j errors, although this does not stop the CLI from working.
-
If a 0-byte file exists, the Domino CLI does not upload the Dataset or Dataset Snapshot.
-
When a project owner is an organization, you cannot change the Workspace and Jobs volume size.
-
The Files page does not render in Domino projects using the Domino File System (DFS).
-
When using the example code app-flask.py in the quick start project to test the redirect sample, the request is blocked.
-
When using the Domino Minimal Distribution (DMD), it fails to install some dependencies.
-
The cursors appear in the wrong location when editing compute environments using Chrome browser on Windows.
-
When Flask apps generate links, this can result in unwanted
302 redirect
behavior. This issue is fixed in Domino 5.2.0.
-
The Import Project drop-down does not display projects owned by organizations of which you are a member. This issue is resolved in Domino 5.2.0.
-
In a Git-based project,
requirements.txt
must be in your project’s Artifacts folder in order to be picked up by an execution, instead of at the root level in your project files.Tip