Add setup_for_company to onboarding status json

What does this MR do and why?

What

Add setup_for_company to onboarding status json

  • Adds setup_for_company to user_detail_onboarding_status.json schema

Why

Similar to !173731 (merged), we must add them first here due to our setting of "additionalProperties": false before using and deploy it out to the entire GitLab.com environment. If we do not deploy this before using we could get into a case where we store a value on canary and then try to save a user update on non-canary and cause an error on user validation. See #461404 (closed) for more info on it.

References

Edited by Jessie Young

Merge request reports

Loading