We need a reliable method of creating test accounts for running as part of autopilot test suites. This requires us to be able to create and authenticate an online account for use during the application test.
Speaking with mardy, it was suggested to use the accounts console plugin. However, we need to ensure access to this is maintained without user prompt.
Per our conversation;
<mardy> balloons: soon we'll enforce access control on the accounts
<mardy> balloons: meaning that before an app will be able to use an account, it needs to ask permissions to the user
<mardy> balloons: and this will involve popping up a UI, and doing some stuff
<balloons> mardy, will there be a way to avoid doing that for our tests?
<mardy> balloons: yes, it makes sense that we add a new parameter to the account-console tool, to add a certain app to the ACL
This bug is to ensure those ACL changes allow us to continue to use the tool once access control lands :-)
Marking this as fixed released, due to the implementation we were able to do inside lp:reminders-app.