FOPTS-6034 Make Azure New Marketplace Products Policy Support MSP Configurations

[midir99]

Description

We changed the method used to obtain the bill connections, now instead of calling the bill-connects API we fetch cost data and get the bill connections from there, this change is required since MSP customers have a different way of configuring their bill connects, and that method would make the policy fail.

This also adds support for MCA connections.

Code change used here is based on already tested code for policy template Azure Savings Realized from Reservations.

Issues Resolved

• https://flexera.atlassian.net/browse/FOPTS-6315 (Refactor Azure New Marketplace Products policy)

Link to Example Applied Policy

• https://app.flexera.com/orgs/1105/automation/applied-policies/projects/60073?policyId=6786e49cc605973ecfa7a53f

Contribution Check List

• New functionality includes testing.
• New functionality has been documented in the README if applicable
• New functionality has been documented in CHANGELOG.MD

IMPORTANT ❗❗❗

Please ignore the following message:

The linter is not able to tell that the script that this datasource uses puts the parameters according to the rule we have:

[github-actions]

1 Error

🚫

operational/azure/marketplace_new_products/azure_marketplace_new_products.pt run_script statements found whose parameters are not in the correct order. run_script parameters should be in the following order: script, val(iter_item, string), datasources, parameters, variables, raw values: Line 256: ds_current_products_oldconnection / run_script $js_get_products_oldconnection Line 355: ds_current_products_newconnection / run_script $js_get_products_newconnection Line 447: ds_current_products_mcacbiconnection / run_script $js_get_products_mcacbiconnection

	1 Warning
⚠️	operational/azure/marketplace_new_products/azure_marketplace_new_products.pt Policy template updated but associated README.md file has not been. Please verify that any necessary changes have been made to the README.

	1 Message
📖	Github Pull Request Pull Request is missing READY-FOR-REVIEW label. Please add this label if this Pull Request is ready for review. Please note that this message may be a false positive if you've added the label after Dangerfile tests were run, since adding labels does not trigger them to run again. In these cases, simply ignore this message.

Generated by 🚫 Danger