[MAGNOLIA-8341] As a developer, I need a feature flag to enable servlet though annotation or web xml Created: 10/Mar/22 Updated: 02/Sep/22 Resolved: 02/Sep/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | David Lopez | Assignee: | Fernando Cherchi |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | nucleus | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||
| Epic Link: | Externalize JCR configuration | ||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Rabie Hayoun [ 10/Mar/22 ] |
|
Add a flag on the bypass and the filter manager to turn on and off this feature. the flag should be done using microprofile |
| Comment by David Lopez [ 14/Mar/22 ] |
|
Hey rhayoun , Is awesome to adopt already feature flags agarcia and/or me would be totally up if you would need any kind of help or if you would like to know more details on how we did it for the hackathon (most likely for technicalities Andres would be right person) |
| Comment by Rabie Hayoun [ 17/Mar/22 ] |
|
Feature flag project has 3 submodules:
This is not a configuration, this is a feature flag |
| Comment by Dominik Maslanka [ 18/Mar/22 ] |
|
is this feature flag use case or regular setting we want to implement rhayoun |
| Comment by Rabie Hayoun [ 21/Mar/22 ] |
|
feature are per use case not a regular setting, at some point we should delete it and get rid of the old code. |
| Comment by Rabie Hayoun [ 03/May/22 ] |
|
Discovery:
|
| Comment by Fernando Cherchi [ 29/Aug/22 ] |
|
Discovery:
|
| Comment by David Lopez [ 02/Sep/22 ] |
Discussion grooming 02/09/2022At this stage we see too much complexity on the approach and might be easier to enable/disable and see what are the consequences. Hence closing. However research is valid in case in the future we would need to come back to the approach we can re-open it. fcherchi , if any follow up ticket is required to proceed with the straightforward approach, let me know.
|