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:
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:
•If you want to pull an object that uses a connection or runtime environment, be sure that the organization includes a connection and runtime environment before you perform the pull. When you select an object that uses a connection or runtime environment, you can select a runtime environment and connection to use on the test page.
•Informatica Intelligent Cloud Services doesn't consider capitalization in object names. As a result, you can't pull a project that contains multiple assets that have the same name with different capitalization. For example, if you try to pull a project that contains an asset named "sales" and an asset named "SALES", you receive an error because a project or folder can't contain multiple assets with the same name.
•You can pull objects regardless of whether your organization can or cannot update the source control repository.
Project and folder pulls
You can pull all of the objects in a project or folder, or pull only the objects that changed in a particular commit hash.
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.
If you pull a project or folder, the pull doesn't affect any objects in the project or folder that aren't source-controlled.
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. You can pull a single asset, a project, or a folder. When you pull a project or folder, you can exclude any assets in the project or folder that you don't want to include in the pull.
To pull a project, folder, or single asset, perform the following steps:
1To pull a project, on the Explore page, click Pull from Git. Select the project that contains the objects you want to pull and click Next.
2To pull a single asset or folder, on the Explore page, select the asset or folder. Click Actions and select Pull.
3Select the Git hash that you want to pull and click Next.
4Review the list of assets. You can clear the check box for any of the assets that you don't want to include in the pull. By default, all of the assets are selected.
5Review the actions in the Status column for each asset. These actions will occur when the pull action is performed.
6 If an asset 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.
7If an asset 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.
8To publish assets after you pull them, select Publish Application Integration assets after pull and Publish Taskflow(s) after pull as required.
9Optionally, click Test to see if errors might occur as a result of the pull action.
10Click 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.
