Fixed issues
Release 11.0.0 changes
Bug Number | Description |
APIGW-5052 | Fixed an issue where the dSource summary name was showing the VDB name while provisioning a VDB in DCT when you get to the summary screen, before submitting the job. |
APIGW-5511 | Added the ability to unregister engines in the UI. |
APIGW-5585 | Fixed an issue where users were unable to logout following SSO token expiration. |
Release 10.0.1 changes
Bug Number | Description |
APIGW-5406 | Fixed an issue where the VDBGroup update API gives an internal error if vdb_ids are the same as ones already present in VDBGroup. |
APIGW-5419 | Fixed an issue where the VDBGroup delete API gives a 404 error if underlying VDBs are already deleted or not present. |
APIGW-5418, | Fixed an issue where VDB provisioning via DCT GUI fails with, “There was an error trying to process your request.” |
APIGW-5570 | Fixed an issue preventing the link of a Postgres database as a dSource. |
APIGW-5571 | Fixed an issue where the Provision VDB -> dSource Listing would not show more than 25 items. |
APIGW-5574 | Hyperscale datasets tables-or-files list and search APIs now return all instead of filtering by dataset. |
APIGW-5578 | Fixed an issue where Pagination was not working for some of the pages in a testing environment. |
Release 10.0.0 changes
Bug Number | Description |
---|---|
APIGW-3931 | Fixed an error found when loading the LDAP config page in the UI, if the LDAP config domains have empty values. |
APIGW-3961 | Fixed the issue where the Environment link to the dSource detail view is broken. |
APIGW-4270 | Cleaned up pending jobs left by deleted engines. |
APIGW-5056 | Addressed VDB provisioning failures where there were a lot of concurrent requests. |
Release 9.0.0 changes
Bug Number | Description |
---|---|
APIGW-3772 | Replicated VDBs/dSources are now identified in the Provisioning wizard. |
APIGW-3931 | Fixed a null pointer exception during LDAP configuration without a domain. |
APIGW-3979 | Fixed an issue where the Import VDB Configuration templates dialog was showing the engine ID in error messages. It is now changed to show engine names. |
APIGW-3983 | Fixed an issue where a new masking job could not be started from DCT when the previous job was cancelled on the masking engine. |
APIGW-4009 | Fixed an issue where the first and last name will be cleared if incorrect names were entered for SSO. |
APIGW-4010 | Fixed an issue in the UI where first and last name attributes cannot be reset. |
Release 8.0.1 changes
Bug Number | Description |
---|---|
APIGW-4324 | Fixed an issue where users who upgraded to DCT 8.0.0 were not able to interact with the UI or connect to the GraphQL service container. |
APIGW-4317 | Fixed an issue where an error would occur when searching for a VDB in the relative refresh UI. |
Release 8.0.0 changes
Bug Number | Description |
---|---|
APIGW-3764 | Removed THE requirement on setting credentials if a masking job execution happens on the origin engine. |
APIGW-3771 | Allows the policy name to be empty when provisioning a VDB. |
APIGW-3783 | Allows for an existing ImagePullSecret to be provided to to pull docker images. |
APIGW-3985 | Fixed the "VDB Container is part of a container" error while refreshing from bookmark directly on the VDB > Bookmark tab. |
APIGW-3990 | Fixed the broken view for a bookmark that has multiple VDBs on the Data > Bookmark tab. |
Release 7.0.1 changes
Bug Number | Description |
---|---|
APIGW-3592, | Previously, a non-admin user that was granted access to a VDB, but not its environment, would get an error accessing the VDB overview. A fix has been implemented to show that the access error is with the environment and not the VDB. |
APIGW-3775 | Fixed an issue where refreshing from the bookmark wizard was not showing compatible bookmarks. |
APIGW-3831 | Fixed a certificates import failure if the truststore is on OpenShift. |
Release 6.0.1 changes
Bug Number | Description |
---|---|
APIGW-3460 | Fixed a request timeout issue. |
APIGW-3395 | Fixed an issue where the refresh wizard did not update snapshots when selecting different datasets. |
Release 6.0.0 changes
Bug Number | Description |
---|---|
APIGW-3223 | Fixed an issue where DCT failed to get info from detached dSources. |
Release 5.0.3 changes
Bug Number | Description |
---|---|
APIGW-3344 | Fixed an issue causing provision failure from RAC dSource to non-RAC target. |
Release 5.0.2 changes
Bug Number | Description |
---|---|
APIGW-2979 | VDB refresh will no longer fail if the refresh target name is not unique. |
APIGW-2981 | Fixed an issue where all the Compliance jobs and source jobs on the engine will be deleted when a Compliance engine is unregistered. |
Release 5.0.1 changes
Bug Number | Description |
---|---|
APIGW-2463 | The default docker-compose.yaml file is now provided with log size and rotation configured for all containers. |
APIGW-2735 | Fixed an issue where DCT migration failed with "could not create unique index environments_host_pkey". |
APIGW-2828 | Helm chart now allows cronjob resource limits to be set via the values.yaml. |
Release 3.0.0 changes
Bug Number | Description |
---|---|
APIGW-1785 | Fixed an issue where Nginx sometimes failed to start after a server restart. |