add_unique_identifier_to_task
Add a unique identifier to a task's appTags to differentiate applications when multiple tasks share the same appType but need separate applications.
Instructions
Add a unique identifier key-value pair to a specific task's appTags.
Use this when multiple tasks share the same appType but need DIFFERENT applications. The unique identifier allows the system to match each application to its specific task.
WHEN TO USE:
After prepare_applications_for_execution() identifies tasks needing differentiation
When user chooses "separate applications" option for tasks with same appType
Before configuring separate applications for same appType tasks
NOT NEEDED WHEN:
User wants to SHARE the same application across multiple tasks
Task already has a unique appType (no other tasks share it)
WORKFLOW:
Call prepare_applications_for_execution()
If user chooses separate applications for an appType:
Call this tool for each task to add unique identifier
Use same key but different values (e.g., "purpose": "source" vs "purpose": "target")
Configure applications with matching identifiers
Args: rule_name: Name of the rule containing the task task_alias: Alias of the task to update identifier_key: Unique identifier key (e.g., "purpose", "sourceSystem") identifier_value: Value for the identifier (e.g., "source-repo", "production-db")
Returns: Dict with update status and guidance
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rule_name | Yes | ||
| task_alias | Yes | ||
| identifier_key | Yes | ||
| identifier_value | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||