The thing is that you're trying to mix old tasks (tasks.yaml) and new tasks (deployment_tasks.yaml). We never supported priority (e.g. 'post_deployment/8100') in deployment_tasks.yaml. It's something we had in tasks.yaml, before granular deployment in Fuel.
In deployment_tasks.yaml we have 'requires' and 'required_for' fields, which should be used for making ordering between tasks.
So the bug is Invalid, actually.
One more thing - tasks.yaml doesn't go through global deployment graph.. moreover, they don't have any deployment graph, they are executing one-by-one according to priority specified in stage.
Alex,
The thing is that you're trying to mix old tasks (tasks.yaml) and new tasks (deployment_ tasks.yaml) . We never supported priority (e.g. 'post_deploymen t/8100' ) in deployment_ tasks.yaml. It's something we had in tasks.yaml, before granular deployment in Fuel.
In deployment_ tasks.yaml we have 'requires' and 'required_for' fields, which should be used for making ordering between tasks.
So the bug is Invalid, actually.
One more thing - tasks.yaml doesn't go through global deployment graph.. moreover, they don't have any deployment graph, they are executing one-by-one according to priority specified in stage.