@fwyzard please review and add a concrete use case.

I assume you need to know when the data is requested and not just when the 'on demand' producing or reading of the data product is activated.

assign core

New categories assigned: core

@Dr15Jones,@smuzaffar you have been requested to review this Pull request/Issue and eventually sign? Thanks

A new Issue was created by @Dr15Jones (Chris Jones).

@davidlange6, @smuzaffar, @Degano, @davidlt, @Dr15Jones can you please review it and eventually sign/assign? Thanks.

Following commands in first line of a comment are recognized

• +1|approve[d]|sign[ed]: L1/L2's to approve it
• -1|reject[ed]: L1/L2's to reject it
• assign <category>[,<category>[,...]]: L1/L2's to request signatures from other categories
• unassign <category>[,<category>[,...]]: L1/L2's to remove signatures from other categories
• hold: L1/all L2's/release manager to mark it as on hold
• unhold: L1/user who put this PR on hold
• merge: L1/release managers to merge this request

@Dr15Jones , was this implemented? should we close this issue?

The use case I had in mind was: given a monolithic CMSSW configuration, how to determine which ESProducers, ESSources, and "global tag" payloads are used by each other ES module and ED module.

This should allow us - for example - to break up the EventSetup mess that is the HLT menu, and keep track of which Path uses which ES object.
It might even allow use to assign the ES modules to the same Tasks as the ED modules to keep things tidier.

@smuzaffar effectively, the esConsumes is doing this.

PR #46929 was just submitted and is available for review. It is an attempt to satisfy the request in this Issue.

cms-bot internal usage