Asset Management > Source control > Source control pulls

Source control pulls

Pull an object to add it to the organization or replace the version of the object in the organization with the version in the source control repository. You can pull a project, folder, or an individual object that isn't checked out by another user.
Before a pull takes place, you can review the potential results of the pull. You can cancel the action or select objects to exclude from the pull.
The following image shows a preview page with potential results in the Status column:
The preview page shows that one of the objects is missing dependent objects so the pull will fail unless this object is removed from the pull or the dependent objects are added. The preview page shows that other objects in the pull action will be overwritten.
You can also test the pull to see if any errors might occur. If any errors appear, you can exclude the objects from the pull or close the page to cancel the pull.
A pull doesn't include dependent objects. For example, in Data Integration, if you pull a mapping that uses a saved query, the pull doesn't include the saved query.
A pull doesn't change the state of pulled objects in the organization. For example, if an object was checked out before the pull, it remains checked out after the pull.
Consider the following rules and guidelines:

Project and folder pulls

You can pull one or more projects or folders.
A pull includes all of the objects within the project or folder. If an object in the project or folder is not source-controlled, the pull does not affect the object.
You specify the version of the objects that you want to pull. The versions of an object that you can select are based on the object's current location in Informatica Intelligent Cloud Services. For example, you check out version 5 of the m_customers object and move it to a project called NewCustomers. When you pull the object, the available versions do not include the versions of the object from the previous location.
A pull updates the project or folder in the organization to be identical to the selected version of the project or folder in the repository. For example, if you pull an older version of a project and the project in the organization contains objects that were added in later versions, the pull deletes the objects.

Pulling an object

Use the pull action to update the organization with objects in the source control repository.
To pull a single asset, you can select the asset and then click Actions and select Pull. To pull a project, folder, or multiple assets, perform the following steps:
    1. On the Explore page, click Pull from Git.
    2. Select the project that contains the objects you want to pull and click Select.
    The preview page appears with a list of available versions of the object. If the pull is for multiple objects, the preview page lists all of the versions in the repository.
    3. Select the version that you want to pull and click Pull.
    4. On the preview page, review the actions in the Status column for each object. These actions occur when the pull action is performed.
    5. To exclude any objects from the pull, clear the check box by the object name.
    6. If an object requires a connection, select a target connection to use in the organization or accept the default.
    Note: You can't create a new connection during the pull process.
    7. If an object requires a runtime environment, select a target runtime environment to use in the organization or accept the default.
    Note: You can't create a new runtime environment during the pull process.
    8. Click Test to see if errors might occur as a result of the pull action.
    9. If the test is successful, click Pull.
    The pull action generates a log showing details of this action. You can view the log on the Source Control Logs page in Monitor.