Open boost enrollment #2264

Ticket(s) / Related Merge Requests

#2264 (closed)

Summary of Changes

Allocation into open boost for users opted in via social compass quiz meeting thresholds defined in #2264 (closed)

Testing Considerations

@tanyatech I am going to push up some front-end changes NOT TO BE MERGED OR QA'd that solely exist so that you don't have to keep making an account every time you answer the questionnaire. I'm going to force the component to show all of the time so expect weird behavior there, but you will be able to answer, re-open, answer, re-open etc - just to make life easier. This MR is solely on the engine side so short of any weird errors being thrown, it won't affect the front-end at all. I'm not even going to link it in this MR, but note it is there.

Acceptance criteria in #2264 (closed) are thorough, check that out.

The CLI portion of this will NOT be testable without K8s setup. To manually run the job you need to:

# copy pod name from below
kubectl get pods | grep open-boost 

kubectl exec -it [pod name] sh

cd engine

# set up your answers and setting as required
php cli.php OpenBoostAllocator

# can use dry run flag to see how many users would be changed.
php cli.php OpenBoostAllocator --dry-run

# check it updated or didn't depending what you were testing

Regression Scope

Effects what happens on social compass answer, and the CLI portion saves state to the user objects.

Platform Affected (web, mobile, etc)

Engine changes - Web / Mob both have the compass.

Developer Testing Completed

Specs and manually testing against and beyond the acceptance criteria.

Screenshots

Does this impact

• Localization
• Dark/light mode
• Guest mode