Connecting to data sources in a Git-based project

When you connect to a data source from a Git-based project, you can connect with a reference or a copy of a platform connection that has already been created, or you can create a new connection in the project.

Platform connections are created by a user with the Editor or Administrator role for the Platform assets catalog. To be available in a Git-based project with default Git integration, the platform connection must be created with personal credentials. (Each user provides their own credentials to use the data source.) You can then create a connection as a reference or as a copy of the original platform connection and then use the connection in various services and projects across the platform.

Check to see if a platform connection is available for the data source that you want to connect to. Otherwise, you can create a new connection in the project.

To connect to data source in a Git-based project:

  1. Go to the project page, and click the Assets tab.
  2. Click New asset > Connect to a data source.
  3. Select a data source type, and then choose the connector.
  4. Choose the kind of connection:
  • Click Select a connector to create a new connection in the project (default).
  • Click Select a platform connection to select a connection that has already been created at the platform level.
    You have two choices:
    • Connection that is a reference to the original platform connection: This is the default option. Use this choice if you plan to use the connection within a single instance of the platform. The benefit is that if the original platform connection is updated, the changes are automatically updated everywhere that the connection was added. The disadvantage is that the connection will not work if the repo is used in a different instance. For example, if you move from a testing environment to a production environment, you will need to edit the connection and update the connection details.
    • Connection that is a copy of the original platform connection: Select Create a copy if you plan to use the connection across multiple instances. A new connection with the same details will be created. Because the connection is a copy, if the original platform connection is changed, the changes are not transferred to the copy. The advantage of this choice is that you can use the connection in a different instance. See Restrictions. This option is available only for a Git-based project with default Git integration.

See Adding connections to project for more information about connections.

Restrictions for connections that are created as a copy of the original platform connection

The following connections do not work as a copied connection in an instance other than the instance where the connection was originally created:

  • Storage volume connection if the volumes are set up differently in different instances.
  • Connections that store credentials or certificates in a secret in a vault. Workaround: Set up new secrets on a vault in the new instance and configure the connection credentials to use those secrets.
  • Connections that use JAR files that you uploaded. For example, for a Generic JDBC connection. Workaround: Upload the JAR files in the new instance and edit the connection to use the JAR files.

Parent topic: Projects with default Git integration