Introduction
During the migration process from a self-hosted environment to a JFrog SaaS instance, there is a limitation regarding artifact properties exceeding 2.4k characters in length. The JFrog CLI, utilized for this migration, indicates the presence of properties with lengths greater than 2.4k characters but does not specify which artifacts possess these oversized properties. This documentation outlines a method to identify the specific artifacts along with the length of their properties.
Resolution
Steps to get the impacted artifacts with the properties longer than 2.4K:
- Configure the source server and the target server using the JFrog CLI command, ensuring the plugins are in place on both the source and target servers. Then, perform the configuration transfer by following the documentation.
- Once everything is in place, execute the transfer-files pre-checks command jf rt transfer-config source-server target-server --prechecks.
- We will get an error if the artifact properties exceed 2.4k characters, as seen in the screenshot below:
- To identify the artifacts associated with these oversized properties, run the following database query to fetch the details directly from the database:
SELECT
nodes.repo,
nodes.node_path,
nodes.node_name,
node_props.prop_key,
char_length(node_props.prop_value) AS prop_value_length
FROM
nodes
INNER JOIN
node_props ON nodes.node_id = node_props.node_id
WHERE
char_length(node_props.prop_value) >= 2400;
Note:
This query is written for a PostgreSQL database, but it can be adapted for use with other database systems as needed.
For reference, a screenshot illustrating the results of this query is attached.
Conclusion
Thus, the artifacts with properties exceeding 2.4k characters in length can be identified and corrected prior to the migration.