depends_on keyword not working as expected
See original GitHub issueWell basically this code just doesn’t compile.
But the whole docs section is confusing. For example, it says
you will still need to set dependencies when you have a relationship between builders, such as setting the key of a storage account on a web app.`
Which I guess is not correct actually, things seem to work fine without the keyword.
Looks like there are issues at least for a month, see this blog post.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why Gradle is not running dependent tasks - node.js
The problem is with the task keyword in statement task war.dependsOn(npmInstall, npmBuild) . To instruct Gradle to execute npmInstall and ...
Read more >Azure/bicep - dependsOn not allowed on existing resources
I would put the dependency on the module that creates the resource group. Can you share the full code sample and what is...
Read more >Resource dependencies using DependsOn - PowerShell
The DependsOn key can be used in any Resource block. It is defined with the same key/value mechanism as other Resource keys. The...
Read more >Iterative Insertion example doesn't validate when ...
Job B depends on job A which creates a cycle in the dependency graph. Is this expected behavior when using the Iterative Insertion?...
Read more >What are TestNG Dependent Tests and How to make ...
A single dependent test in TestNG is declared when a single test depends on another test. It is similar to the example we...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is probably just a case of documentation being out of date. In the earlier versions of Farmer, you explicitly had to supply
depends_on
all the time. In more recent releases, wherever we can, we infer the owner of any expressions and automatically set that resource as a dependency.I’ll have a look through the blog post though - obviously we’re not monitoring every blog out there so thank you for pointing it out to us.
It’s also possibly that there is a breaking change in either removal of an overload for
depends_on
, or an issue in overload resolution across generic lists (which F# is quite strict on).For completeness, here’s the updated documentation.