5B. [Repositories] Publishing and Using Shared Libraries in Code Repositories3. Creating A Shared Repository

3 - Creating a Shared Repository

This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.

📖 Task Introduction

If you or your colleagues have build code that should be shared throughout your enterprise, you’ll start by creating your own designated Conda library repository.

🔨 Task Instructions

  1. Open your /Data Engineering Tutorials folder (e.g., .../Temporary Training Artifacts/yourName/Data Engineering Tutorials/).

  2. Create a new folder called Shared Python Libraries.

  3. In your new Shared Python Libraries folder, create a new code repository.

  4. On the Initialize Repository screen, name your repository yourName_cleaning_functions (e.g., jmeier_cleaning_functions).

    • ℹ️ The name of your repository serves as your library name, so it’s important that it be unique to avoid name collisions. You can rename it later by accessing the hidden gradle.properties file and editing the condaPackageName parameter (described below).
  5. Click into the Python Library block (i.e., not the Data Transforms block) and then on the blue Initialize repository button.

  6. Once your repository opens, click on the cog/gear icon just beneath the branch name.

  7. Move the Show hidden files and folders toggle to the “ON” position.

  8. Locate and click on the gradle.properties file. The top line provides the condaPackageName, which is the name of your repository by default. This is where you can come to change the name of your package if desired.

Please be aware that spaces or underscores in your repository name will be replaced with hyphens in the package name.