This operation saves the name of the deployment group that will be migrated. It doesn't contact the server at all. It can be run on any endpoint, whether the FlexDeploy local server endpoint, an Informatica server, or any other working endpoint. Pass in at least one of the 2Â Deployment Group Name options either Project Property or Plugin Input.
This provides you with two possible options for Project Setup.
- Project by Deployment Group
- Configure Deployment Group Name on Project Properties.
- Do not use anything for Plugin Input for Deployment Group Name.
- It is advisable to keep Project Name same as Deployment Group Name for clarity.
- This option works well with Release Snapshot and Pipeline based execution and helps with continue delivery.
- Adhoc Project to perform Build and Deploy using Input for Deployment Group name.
- Do not use anything for Deployment Group Name on Project Properties.
- Configure Workflow Input to be passed in to Plugin Input for Deployment Group Name.
- This option works for Adhoc deployments but it will not fit in Release and Pipelines.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Deployment Group Name | FDI_DEPLOYMENT_GROUP_NAME | No | Use to pass in the name of the deployment group to migrate. Defaults to the project name, so consider creating a project per deployment group that you wish to migrate. |
...
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Deployment Group Name | FDI_DEPLOYMENT_GROUP_NAME | No | Use to pass in the name of the deployment group to migrate. Overrides the project property of the same name. |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
...