Do not check for jitsu_key
What does this MR do and why?
This MR does two changes
- Refactor
InitializeStackService
- Move auth and status checks outside of
feature_availability_error
as recommended in a previous MR. - Move status checks to a
status_error
helper
- Remove usage os
jitsu_key
inInitializeStackService
as part of jitsu related backend code cleanup
No changelog trailer is added as the feature was behind a feature flag.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #406659 (closed)
Edited by Halil Coban