[MGNLCT-264] Implement checking the feature toggle in #initialize of NorsuContentTypeInitializer Created: 08/Aug/22 Updated: 09/Feb/23 Resolved: 19/Sep/22 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Oanh Thai Hoang | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | SaaS TPR - ContentTypes |
| Team: |
| Description |
|
Delaying Datasource initialization until needed.
From Mika proposal regarding JCR content-types: JCR content-types, they need to work side by side, otherwise we directly affect our trialists. We could also introduce the "opposite" feature toggle for restricting JCR gradually, to make sure new production customers do not create JCR content or config-entities, until we pull the plug. Error log when initializing norsu content type: extract-2022-08-08T01_00_31.170Z.csv |
| Comments |
| Comment by Rabie Hayoun [ 08/Aug/22 ] |
|
So right now, we don't have Norsu enabled on production. We are working on it. it should be up and running in a few weeks. So we need to avoid initialization of the Norsu API at start up, because that it's blocking the deployment and magnolia start up. Maybe with my workaround is more than enough until we create prod cluster and deploy the DB. we could try it and if it doesn't work we can add. the feature flag then |