Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-orchestrator fusiondirectory-orchestrator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-orchestratorfusiondirectory-orchestrator
  • Issues
  • #97
Closed
Open
Issue created May 20, 2025 by dockx thibault@tdockxMaintainer

[Orchestrator] - lifeCycle when target resource does not exist - a different description should happen than a pure success

[Orchestrator] - lifeCycle when target resource does not exist - a different description should happen than a pure success

When we run a pre set resource but an empty destination resource ( such as account not existing ). The task will succeed but the description should be changed from Account states have been scucessfully modified for to no modification was actually required as destination resource is not existing.

Assignee
Assign to
Time tracking