[FREEZE-9] personalizationActivation command does not check for freeze Created: 08/Jul/20 Updated: 04/May/22 Resolved: 08/Jul/20 |
|
| Status: | Closed |
| Project: | Freeze |
| Component/s: | None |
| Affects Version/s: | 1.7 |
| Fix Version/s: | 1.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Warinner | Assignee: | Andrew Warinner |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Description |
|
The command /modules/personalization-core/commands/default/personalizationActivation does not check for an active freeze before publishing. default-personalizationActivation is invoked by the publishing workflow after approval and is also used by scheduled publishing. |