[MAGNOLIA-7810] Fail when specified configuration profile doesn't exist Created: 25/May/20 Updated: 24/Jun/20 Resolved: 16/Jun/20 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Michael Duerig | Assignee: | Michael Duerig |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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)
|
||||||||||||||||
| Epic Link: | Product improvements for Cloud project features | ||||||||||||||||
| Sprint: | TE 4 | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
|
Since To implement this we need to clarify what it means for a profile to exist. As an initial approach I suggest to only implement this for the case where PROFILE_INITIALIZATION_PARAMETER is not overridden and in this case fail if the directory WEB-INF/config/${env/MAGNOLIA_PROFILE} does not exit. Further refinements like checking if the directory is non empty or even whether it contains files that are actually resolved would be possible but could easily become unwieldy. |