Index
addResourcePoolToEnvironmentTieraddResourceTemplateToEnvironmentTemplateTieraddResourceToEnvironmentTemplateTiercreateEnvironmentTemplatecreateEnvironmentTemplateTiercreateEnvironmentTemplateTierMapcreateHookcreateResourceTemplatedeleteEnvironmentTemplatedeleteEnvironmentTemplateTierdeleteEnvironmentTemplateTierMapdeleteEnvironmentTemplateTierMappingdeleteHookdeleteResourceTemplategetAvailableResourcesForEnvironmentgetEnvironmentTemplategetEnvironmentTemplatesgetEnvironmentTemplateTiergetEnvironmentTemplateTierMapsgetEnvironmentTemplateTiersgetHookgetHooksgetProvisionedEnvironmentsgetResourcePoolsInEnvironmentTiergetResourcesInEnvironmentTemplateTiergetResourceTemplategetResourceTemplatesgetResourceTemplatesInEnvironmentTemplateTiermodifyEnvironmentTemplatemodifyEnvironmentTemplateTiermodifyEnvironmentTemplateTierMapmodifyEnvTemplTierResourceTemplMappingmodifyHookmodifyResourceTemplateprovisionEnvironmentprovisionResourcePoolremoveResourceFromEnvironmentTemplateTierremoveResourcePoolFromEnvironmentTierremoveResourceTemplateFromEnvironmentTemplateTier
getPluginCatalog
getServerSettingsCategories
processWebhookTrigger
getWorkItems

createApplicationDependency

Back to index

Summary

Defines a dependency of an application (or its snapshot) on another application (or snapshot). At runtime, the deployment process checks for the dependent applications on the environment. The deployment stops if dependent applications or their versions are not present and you have requested enforcement of the dependency check. Otherwise, the deployment continues with a warning.
projectName
Stringrequired
The name for the project that must be unique among all projects.
applicationName
Stringrequired
The name of the application.
applicationDependencyName
Stringoptional
The name of application dependency. If not specified, a system generated GUID is used.
dependentApplicationName
Stringoptional
The name of application which this application depends on.
dependentProjectName
Stringoptional
The name the project containing the dependent application.
dependentSnapshotName
Stringoptional
The name of snapshot of the dependent application.
effectiveDate
Stringoptional
The date when this dependency is applicable (for example, 2023-05-15).
snapshotName
Stringoptional
Name of the snapshot; must be unique within the application.

Usage

Perl

$cmdr->createApplicationDependency(
  "test-projectName", # projectName
  "test-applicationName" # applicationName
  # optionals
);
▼

ectool

ectool createApplicationDependency \
  "test-projectName" `# projectName` \
  "test-applicationName" `# applicationName` \
  # optionals
▼

Examples

Perl

To create a dependency between two component process steps in a master component:

$cmdr->createApplicationDependency('Default', 'Deploy', 'Get WAR file', 'Copy WAR file', {componentName => 'WAR file'});
▼

To create a dependency between two component process steps in a specific application:

$cmdr->createApplicationDependency'Default', 'Deploy', 'Get WAR file', 'Copy WAR file',  {componentName => 'WAR file', componentApplicationName => 'Shopping Cart'});
▼

To create a dependency between two application process steps:

$cmdr->createApplicationDependency('Default', 'Deploy', 'Get WAR file', 'Copy WAR file',  {applicationName => 'Shopping Cart'});
▼

ectool

To create a dependency between two component process steps in a master component:

ectool createApplicationDependency 'Default' 'Deploy' 'Get WAR file', 'Copy WAR file' --componentName 'WAR file'
▼

To create a dependency between two component process steps in a specific application:

ectool createApplicationDependency 'Default' 'Deploy' 'Get WAR file', 'Copy WAR file' --componentName 'WAR file' --componentApplicationName 'Shopping Cart'
▼

To create a dependency between two application process steps:

ectool createApplicationDependency  'Default' 'Deploy' 'Get WAR file', 'Copy WAR file' --applicationName 'Shopping Cart'
▼