The problem you're running into is due to the behavior of ZIO.cond. The way it works is that it WI...
ZIO.cond returns a ZIO type, but it does not directly run the effect you provide as its failure parameter. Instead, it returns a ZIO type that represents either the success or the failure of the condition.
In your case, when you run the program without command-line arguments, ZIO.cond fails, and the first step in the blueprint fails, leading to the 'FAILURE' message being printed out.
To solve this issue, you can combine ZIO.cond with ZIO.foldM, which allows you to define how the ZIO should fold and evaluate based on its result.
[
add
]
[
|
|
...
]