Limit for attributes is applied before the max-depth filter

[kayrus]

Examples:

$ hermesctl attributes action -l5
update
update/add/security-group
create
delete
create/role_assignment

$ hermesctl attributes action --max-depth 1 -l 3
update
create

$ hermesctl attributes action  --max-depth 2 -l 3
update
update/add
create

$ hermesctl attributes action --max-depth 1 -l 10
update
create
delete
read

$ hermesctl attributes action --max-depth 1
update
create
delete
read
stop
allow
disable
deny
restore
start

I assume that the limit should be applied after the max-depth filter.

[notque]

Will look to spend some time on this shortly.

[notque]

Max depth isn't a filter, it's an indication that you want to split out events into composite parts of the hirearchy. This is used with elektra to allow you to explore the events based on the parts.

If you placed limited after the max depth, it wouldn't make any sense as you'd end up cutting off parts of the hirearchy. You're limiting the number of events that are returned, not the parts of the hirearchy that would come back.

Does this make sense?

[kayrus]

this is not an expected behavior, but your explanation makes sense. thanks.

[notque]

I will update the docs to try to make this clearer.