x/authz design should not require a cyclic dependency to function

[kocubinski]

Problem

The current x/authz design has modules x/bank and x/staking implementing authz.Authorization, which contains a reference the authz.AcceptResponse. This means that modules implementing Authorization must depend on x/authz which is already a bit of an anti-pattern.

CmdGrantAuthorization in x/authz depends on x/bank and /x/staking, forming the cyclic module relationship.

Possible Solutions

1. Push AcceptResponse down into sdk/types, and change Updated field type to proto.Message. Refactor usages.
2. ADR-33 style plugin system (details forthcoming)

[aaronc]

Should we just switch to autocli?

[kocubinski]

Should we just switch to autocli?

Maybe, what's the timeline for that as viable production ready replacement though?

[aaronc]

Should we just switch to autocli?

Maybe, what's the timeline for that as viable production ready replacement though?

No idea, we need to decide who is going to work on transaction support and when we prioritize that.

For authz cli we probably should just expect a json authorization instead of trying to cover so many use cases