This message was deleted.
# contributors
b
This message was deleted.
👍 1
w
huh, that’s an interesting thought, I hadn’t considered it as I thought it’s useful to explain how things are priced for the user even if we don’t know the costs upfront. It might be worth exploring something like
--show-skipped
for this though
b
for "cost depends on usage" lines, it def makes sense to see them there .. but if usage and price are known, and their product is 0 for a given cost component - it might make sense to skip displaying that component (and possibly skip displaying an entire resource, if its cost is 0).
as for the CLI UX of such a feature, I wonder if a
--verbose
flag would be appropriate. initially this only makes sense for
breakdown
but someday we might figure out what "verbose" means for
diff
or other subcommands.
anyhow -- bigger fish to fry just now, but I might tackle this sometime down the road.
w
if usage and price are known, and their product is 0 for a given cost component - it might make sense to skip displaying that component (and possibly skip displaying an entire resource, if its cost is 0).
Makes sense! We skip 0 cost and free resources altogether when defining them in a resource.go file