Rules and Guidelines for CI/CD REST API Reference
Rules and guidelines to use CI/CD REST APIs. You can refer to the restrictions and use-cases to effectively use the CI/CD REST APIs.
Consider the following rules and guidelines when you use CI/CD REST APIs:
- •Accepts values only from java.time.ZoneID(). For example, IST is not supported.
- •Passwords that are encrypted using the pmpasswd utility must be encrypted using the option -e=CRYPT_DATA.
- •The query parameters are not case sensitive.
- •Reserved characters in older clients must be percent-encoded.
- •Internal descriptions of data types are printed in the output when comparing objects and the field types are different.
- •When you deploy objects to an application patch archive file, the default location of the file is $INFA_HOME/tomcat/bin/target. If the Data Integration Service is configured to use operating system profiles and you specify the operating system profile, the archive file is written to $DISTargetDir instead.
- •When you deploy objects to an application patch archive file, you can specify mapping deployment properties to override the default mapping deployment properties for mappings in the deployed application. Specify each mapping deployment property as a name-value pair. For information about the mapping deployment properties, see the Application Deployment chapter in the Informatica Developer Tool Guide.
- •Archive files must be saved to a shared disk location when deploying objects to an application patch archive file, if a user sends the REST API request directly to a Data Integration Service instead of routing it through the REST Operations Hub.
- •When you deploy objects to an application patch archive file, the result of the query must contain at least one object that can be run, such as a mapping or a workflow.