We need to review all AzDO logging commands used for RO/RW-ness of variables

• This issue is blocking : Not blocking but only because the feature flag was turned off
• This issue is causing unreasonable pain : Same as above, only not unreasonably painful because it’s turned off.

As noted in this build, we’ve started to run afoul of this by-design security improvement change described here.

This was thankfully turned off quickly after it broke us, but will definitely be turned on again.

What we need to do:

• Review everywhere Arcade functionality is writing output variables
• Everywhere we are writing one, if there is any chance of it being written multiple times it needs to have isReadonly=false set.
• Output variables are as noted automatically read-only, if these are set multiple times they will likely need to be refactored in some way.

@ilyas1974 / @markwilkie this isn’t urgent but maybe a candidate for FR. It’s going to be non-trivial amounts of work and it’s not urgent as we’ve gotten the flag turned off for now.

[missymessa]

@vtbassmatt I think I found a build with the warning:

[riarenas]

Worth noting here that even once we make the changes in our repos, we need to sync up with partners and let them know with enough time for them to also do any work in their repos before the feature flag is turned on again.