Andrey Novikov

Released summary support in [yabeda 0.12.0](https://github.com/yabeda-rb/yabeda/releases/tag/v0.12.0) and [yabeda-prometheus 0.9.0](https://github.com/yabeda-rb/yabeda-prometheus/releases/tag/v0.9.0). Thanks for opening the issue and sorry for the long wait!

I don't know much about passenger, but for now I can recommend to either: 1. Export metrics from the main application (e.g. via plugging exporter it in via Rackup or...

Actually it should be fixed on `aws-requests-auth` side, here is the proposed fix: https://github.com/DavidMuller/aws-requests-auth/pull/60

Workaround for the time being to use aws-requests-auth with the fix: ``` pip install git+https://github.com/Envek/aws-requests-auth@fix/multipart-requests pip install httpie httpie-aws-authv4 http --auth-type aws4 --auth REDACTED.execute-api.us-west-2.amazonaws.com \ --multipart POST http://example.com/test field=value ```

Seems like I found solution: will be fixed by https://github.com/apotonick/representable/pull/191 @apotonick can you please take a look and merge it?

Hey, thanks for your contribution! I have one concern and one question: 1. Concern: as operation name is set by clients, tracking it in labels opens a possibility to attacks...

+1 on having some method like `policy_scope` but allowing to retrieve exact scope that you want for this model at time. Writing something like this in every action in, say,...

Also there is [`action_policy`](https://github.com/palkan/action_policy) gem (it is inspired by pundit too) which supports [scoping](https://actionpolicy.evilmartians.io/#/scoping) among other features.

Possibly related issue: https://github.com/helm/helm/issues/3957 --- Here is my big **+1** for this. Frequent use case for which `--reuse-values` works very counter-intuitive is **adding new features to the chart**. It is...

`helm get values foo > values.yaml && helm upgrade foo ./foochart -f values --set ...` definitely works but there is always a little chance that someone or something else will...