fix(consumption-profile): use family and TDP parameters in CPU completion

[Shillaker]

Problems

The CPU consumption profile endpoint:

• Does not currently use the family and TDP parameters from the name completion
• Returns a 500 error if the CPU name fuzzy-match fails

Fix

• Use all relevant values from fuzzy matching to compute consumption profile
• Tolerate unrecognised CPU name (by taking the default)

[da-ekchajzer]

Hum, that is weird, I will have a look this weekend. Is this only a problem when using the CPU route ? When assessing a server or a cloud instance, the CPU TDP is used ? Do you have an exemple that doesn't work ?

[Shillaker]

Yeah it's just the implementation of this endpoint. AFAICT consumption profiles + name lookup works fine elsewhere.

You can test it in Swagger (here). If you send a request with just a CPU name, and vary the name, the results don't change (same if you add a TDP). If you also set some junk name like foobar you get a 500.

[da-ekchajzer]

Perfect tested works for me ! Thank you for the bug fix.