[MAGNOLIA-6215] YAML configuration not removed or de-registered after physical removal Created: 22/May/15 Updated: 18/Apr/16 Resolved: 14/Apr/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | configuration, resource-loader |
| Affects Version/s: | 5.4 |
| Fix Version/s: | 5.4.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Natascha Desmarais | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
5.4 alpha-2 CE and EE bundles |
||
| 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)
|
||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Resource reloading without restart | ||||||||||||||||
| Description |
|
If you remove a java-free module completely or only partially from the filesystem, the definition is still available within admincentral - for example removing a page definition and template, the page still appears as available while adding a page. So it seems that missing configurations are not de-registered properly. |
| Comments |
| Comment by Christopher Zimmermann [ 12/Jan/16 ] |
|
This ticket would be resolved by changes in |
| Comment by Roman Kovařík [ 04/Apr/16 ] |
|
Please also check moving of definitions while tackling this one. Currently the definitions are duplicated (new and old location). |