-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DependingOn not working as expected (ordering wrong) #101
Comments
Hiyo! So it looks like we namespace the dependency name - try using I don't recall the specifics, but I think it was to avoid collisions. I might need to update docs, there's some info here, but at a quick glance didn't see in module docs. Also, in that example... not sure why B wasn't namespaced. Will have to look at the code, might take a few days Let me know how it turns out with the namespaced DependingOn bits! Cheers! |
Yup - using namespaced names works - thank you for your speedy reply |
On another note ... is there a way to setup a task, to only run if specific tasks are used? |
Hi! Completely missed the follow-up, sorry about that! Can you give a quick pseudocode example that you might expect to use if this was in place? Just the ability to use tags for Task deployment types? Just flipped through the code, and I explicitly avoided this for some reason - if you have any ideas on how to implement it, seems like it would handy! |
No worries, and sorry for the late reply. Racking my brain to try and remember what that was all about, but comming up short. |
Using DependingOn results in a deployment order that is completely different from what I expected.
Consider the following psdeploy.ps1 file:
I would expect the order of execution to be:
But what I get is:
Version used:
The text was updated successfully, but these errors were encountered: