[Feature flag] Enable Bill To and Sold To contact management for admins

Summary

This issue is to rollout Bill To / Sold To Contact Management by Admins on CustomersDot production, that is currently behind the key_contacts_management_admin feature flag.

Note: This gates the Bill To / Sold To Contact Management in the context of the CustomersDot Admin.

Owners

Stakeholders

The Rollout Plan

Rollout Feature for everyone as soon as it's tested and approved in staging

Expectations

What are we expecting to happen?

Enhance key contact management for CustomersDot users.

CustomersDot Admins are able to manage the Bill To and Sold To contacts for CustomersDot users via the CustomersDot Admin interface.

What might happen if this goes wrong?

  • Bill To and Sold To contacts for the associated Zuora accounts are not correctly set.
  • Invoicing and delivery of licenses / codes and notifications will go to the wrong people.

What can we monitor to detect problems with this?

  • Keep an eye on Sentry.
  • Check #s_fulfillment_daily for errors.

Rollout Steps

Rollout on non-production environments

  • Ensure that the feature MRs have been deployed to non-production environments, i.e. customers-staging.
  • Consider announcing that the flag will be enabled to potentially impacted groups, e.g. #s_fulfillment_engineering
  • Enable the feature globally on non-production environments by applying the appropriate environment, e.g. customers-staging and customers-development.
  • Notify the Software Engineers in Test (SETs) for Fulfillment via Slack and in a comment in this issue when enabling a feature flag in customers-staging as it can impact the QA pipeline.
  • Verify that the feature works as expected. Posting the QA result in this issue is preferable.

Preparation before production rollout

  • Stub the feature flag as enabled by default in RSpec to avoid unexpected side-effects and ensure better coverage.
  • Ensure that the feature MRs have been deployed to production
  • Check if the feature flag change needs to be accompanied with a change management issue. Cross link the issue here if it does.
  • Ensure that you or a representative in Fulfillment can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the Fulfillment team in #s_fulfillment_engineering
  • Ensure any documentation has been updated
  • Announce on the feature issue an estimated time this will be enabled on production if applicable
  • If the feature might impact the user experience, notify #s_fulfillment and potentially #support_gitlab-com, as well as your team channel (more guidance when this is necessary in the dev docs).

Global rollout on CustomersDot production

Release the feature

After the feature has been deemed stable, the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.

Rollback Steps

  • This feature can be disabled by performing the following actions:
Edited by Tyler Amos