Billing scope to monitor parameter in bicep template seems not to result in an array in the .json setting file in the storage config folder

[AP-RIVM]

🐛 Problem

When using scopes to monitor parameter in Bicep, while deploying the FinOps hub, the billing scope needs to be an array and is an object.

👣 Repro steps

TODO: Add repro steps below:

1. Deploy FinOps hub bicep modules (v0.9) with the public access enabled.
2. Add the scope to monitor parameter: param scopesToMonitor.
3. Look in the .json settings file in the config folder in the deployed storage account.

🤔 Expected

The billing scope should be an array.

📷 Screenshots

🙋‍♀️ Ask for the community

We could use your help:

1. Please vote this issue up (👍) to prioritize it.
2. Leave comments to help us solidify the vision.

[flanakin]

AP-RIVM Are you getting an error anywhere? This is interesting because we actually fixed this in 0.9. I wonder if passing the input is causing an issue we didn't cover in that fix 🤔 Either way, it shouldn't matter because we should be handling both cases (object and array) everywhere. I'd love to know if there's an error cropping up somewhere so we can fix that.

#needs-info

[AP-RIVM]

This error melding appears in the Data Factory.

[flanakin]

AP-RIVM I just looked at this and realized that pipeline already has the fix. The activity you called out may fail, but there's another activity that applies a workaround. This error should not cause the entire pipeline to fail. Can you confirm if the Set Scopes As Array activity was successful?