feat(#BRU-18) : "inherit" auth mode for inheriting auth to requests from collection

[lohxt1]

Inherit auth to requests from collection

inherit_auth_mode.webm

inherit_auth_mode_cli.webm

[helloanoop]

Merged!

Thanks for taking care of this @lohxt1 !

[helloanoop]

@lohxt1 Just a FYI, I have made changes to gracefully handle older collections which are using none and still inherit collection auth.

Plan is to give some time to for users to migrate (and broadcast these via x/discord/communit calls) before causing CI pipelines to break.

See 1cf8a2f

[lohit-bruno]

Got it @helloanoop

[timwsuqld]

@helloanoop is there a way to make none actually None? I want to be able to use inherit, but have a route that needs to not inherit.

[Tydax]

@helloanoop is there a way to make none actually None? I want to be able to use inherit, but have a route that needs to not inherit.

EDIT: Nevermind, this seems to be on purpose to keep a retro compatible behaviour

I can confirm that I have the same issue, it seems that No auth on a request does not “override” the collection authentication setting and defaults to an inherit behaviour. I think this is a bug.

For now, I got it working by manually defining an Authorization header in the Headers tab in the collection's settings and then adding another Authorization header with a blank value on the request that should not use it.

[helloanoop]

Breaking change will be shipped in v1.16.0
After which None means None

[melroy89]

Two tests are failing tho..?

[slowjoe007]

Also figured this in #2057. The tests appear to fail due to this change when executed via bru CLI. The request auth/inherit auth is working inside the GUI though.

[melroy89]

I don't understand why a failing CICD run was merged, causing regression. But yea.