Address mechanizer use case: Subscription and namespace association breaks because of bugs
Why does the use case exist?
There are various bugs in the system that either prevents an association to happen or that unassociates subscriptions and namespaces. These bugs result in manual work for support where a force reassociation is necessary to get the namespace back on their subscription. When a namespace doesn't receive the entitlements of their subscription, this breaks customer trust.
Reference:
- Unable to link subscription due to additional m... (gitlab-com/support/toolbox/console-training-wheels#22 - closed)
- CustomersDot <> GitLab.com Access Token Short E... (customers-gitlab-com#4345 - closed)
Are there any workarounds?
Each bug is unique and their resolution should be addressed separately.
Is the function addressing a bug or a missing feature?
Edited by Donique Smit