Review the effort and category of the Azure rules

[agoncal]

Each WindUp rule has a severity (or effort):

• 0 is just an information
• 1 being the easiest to migrate,
• 13 being the most difficult (which usually means re-architecturing)

This is described in this document:

Level of Effort	Story Points	Description
Information	0	An informational warning with very low or no priority for migration.
Trivial	1	The migration is a trivial change or a simple library swap with no or minimal API changes.
Complex	3	The changes required for the migration task are complex, but have a documented solution.
Redesign	5	The migration task requires a redesign or a complete library change, with significant API changes.
Rearchitecture	7	The migration requires a complete rearchitecture of the component or subsystem.
Unknown	13	The migration solution is not known and may need a complete rewrite.

Make sure we have the right effort points in our Azure rules

As for the categories, WindUp uses the following ones:

• information
• potential
• mandatory

[showpune]

For the resource usage rules like customer is using Redis, DB, it is an INFO with effort 0 or not.

If it is an INFO with effort 0, we have so many technology usage and how can we tell the sales it is important, compared with other technology

[agoncal]

As an example, today we have the following rule concerning Redis:

 <hint title="Redis Cache found in the application" category-id="information" effort="0">

This can be improved in two different scenarios:

• The app can use Redis or can use an Azure managed Redis: The category is then "optional" and the max effort is 5 if the customer decides to use the Azure managed Redis (otherwise it's zero as the rule is optional)
• The app is using Redis and it must be updated to use the Azure managed Redis: The category is then "mandatory" and the effort is 5