Released: 24 January, 2024
Feature Enhancements
Additional Full Sync event property for Federated repositories
A new event property is available when performing Full Sync operations on Federated repositories. This new property retries the attempt to create event bulks (or batches) if the initial attempt fails. For more information, see Configure Federated Repositories for Bulk Event Mirroring and Parallel Processing.
Oracle RAC support for Federated repositories
Customers in Self-Hosted environments who use Oracle Real Application Clusters (RAC) must configure the following Artifactory system property to support Federated repositories:
artifactory.oracle.node.events.sequence.is.no.cacheSetting this property to
trueenables a converter that fixes the Oracle node events sequence definition for RAC instances.Note
For additional prerequisites, see Setup Prerequisites for Federated Repositories.
Resolved Issues
JIRA Issue | Severity | Description |
|---|---|---|
RTDEV-38832 | Critical | Fixed an issue related to SSH keys whereby, when upgrading from Artifactory version 7.59.x-7.63.5 to a newer version and creating authentication SSH keys, the saved authentication SSH keys were lost. |
RTDEV-38770 | High | Fixed an issue related to Terraform whereby, under certain circumstances, modules from remote repositories could not be resolved due to a Terraform update. |
RTDEV-38558 | High | Full Sync operations on Federated repositories now always update the timestamp in the node_event_cursor table. |
RTDEV-38552 | High | Fixed an issue in the batch propagation mechanism for Full Sync operations that sometimes caused parsing exceptions. In addition, a new retry mechanism will fail only after a defined number of attempts. (By default, Full Sync will fail if a batch fails to propagate 5 times.) |
RTDEV-38555 | High | Fixed an issue whereby Full Sync operations could not be triggered again after failing the initial attempt. |