Ian Cooper

@aidanlim90 Let me take a look, this will probably be post v10 as we have a number of changes to how we handle the RDBMS support there

Hi @caustav - I'll need to peer into this unless @Red-F is around, sees this and wants to comment on the capabilities

Thanks

[phuaxinyuin](https://github.com/phuaxinyuin) As part of V10 we are defining semantic conventions for our telemetry which will include the ability to turn off attributes: https://github.com/BrighterCommand/Brighter/discussions/3071

@martincostello Help would be appreciated. I think we have two options. Move in v10 and make v8 style Polly a dependency, or support both syntaxes in our middleware for a...

After a discussion with Martin we are likely to: * Add an enumeration to the UsePolicy(Async) attribute to allow you to choose the API * - Policy for V7 *...

See also: https://github.com/BrighterCommand/Brighter/issues/1197 for Polly issues for V10

There is some useful thinking here about environment checks, particularly as cli check: https://jeremydmiller.com/2019/10/01/environment-checks-and-better-command-line-abilities-for-your-net-core-application/ and it came from this Twitter thread which has some interesting observations: https://twitter.com/RogerAlsing/status/1636273862718398464?s=20 which could relate...

@honkuan86 I think this is part of a generic class of problems where the publication is not made available to the mapper, and this prevents us also letting you create...

In progress as part of V10 work to expose a Publication to a Message Mapper