SKUs environment should be configurable via brave://flags

Test plan

1. Fresh profile
2. Visit brave://flags/#skus-environment
3. On Windows and macOS, there should be a value here (Default, production, staging, development) and it should be configurable. Linux is not supported at this time
4. Enable brave://flags/#skus-sdk - set this new value (brave://flags/#skus-environment) to development
5. Exit the browser. Start Brave via command line making sure to add logging arguments --vmodule="*/skus/*"=1 --enable-logging=stderr
6. Visit https://account.brave.software and log in (@bsclifton can help if basic auth is presented; creds are in 1PW4T or send a DM)
7. Once logged in, buy VPN
8. You should see (in the console where you started Brave) lots of JSON and output from calls which include refresh_order

There may still be environment issues preventing the credentials from being issued… but as long as the refresh_order has details, that means the environment specific part worked 😄

Description

We already have brave://flags entries for both VPN and SKU (dependent on each other for Desktop)

• brave://flags/#brave-vpn
• brave://flags/#skus-sdk

But at the moment, environment is defaulting to production for an official build (otherwise, it uses development).

There is a command line flag --skus-env which accepts the following values:

• production
• staging
• development

It would be great to expose this in brave://flags. If Default, we can default to production. But if overridden, it can use the chosen environment.

[bsclifton]

Updated test plan to mention just looking for refresh_order 👍 and noted about environment issues

[stephendonner]

QA-status update on this: I’ve started testing, but have run into two (related?) issues:

1. Stripe session errors on checkout (Expired) - not 100% of the time, but more than not
2. Neither @bsclifton nor I are seeing fetch_order_credentials from the testplan, but we are seeing refresh_order calls, as expected.

@evq has offered to help take a look; thread here: https://bravesoftware.slack.com/archives/C021S0FN3V1/p1645063771631899

Being honest and marking QA/Blocked until the above two items (and any others further) are resolved. But we have a path forward 👍