How are teams platform admin teams managing "allow list" for libraries feature UC?

[RamlaS]

We have so many team using maven libraries and are in the process of UC migration. These maven coordinates need to be added to "allow list" before they can be used in clusters. What is the standard process followed by admin teams for this feature? Do you have a self service model or how do you process the intake requests for such additions?

[Kaniz_Fatma]

Hi @RamlaS, 

Managing the “allow list” for libraries in Databricks involves ensuring that specific Maven coordinates are approved for use in clusters.

1. Manual Approval Process:

   • Admin teams manually review and approve Maven coordinates.
   • Users submit requests to add specific libraries to the allow list.
   • Admins evaluate the libraries based on security, compatibility, and licensing.
   • Once approved, the libraries are added to the allow list.

2. Self-Service Model:

   • Some organizations provide a self-service portal where users can request library additions.
   • Users submit requests, and the system automatically checks against predefined criteria.
   • If the criteria are met, the library is added to the allow list without manual intervention.

3. Automated Dependency Scanning:

   • Tools like Nexus IQ or Sonatype can scan Maven dependencies for vulnerabilities.
   • Admins set policies to automatically approve or reject libraries based on scan results.

4. Integration with CI/CD Pipelines:

   • Libraries can be added during CI/CD pipeline execution.
   • Admins define rules for library inclusion based on pipeline configurations.

Additionally, consider leveraging Databricks’ built-in features for managing libraries within job clusters. For example, you can install libraries directly from Maven or Python using the “Dependent libraries”...².

Feel free to adapt these practices to suit your specific use case and organizational context! 😊