[MGNLCT-85] Automatic subscribe workspaces configured with YAML Created: 24/Dec/18  Updated: 03/Jan/19  Resolved: 03/Jan/19

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-7415 Versioning and publication for differ... Accepted
causality
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)
Date of First Response:
Visible to:
Darko Stefanovic

 Description   

As described in SUPPORT-9442:

When new application is created and configured via yaml, Magnolia doesn't configure the subscription automatically. Workspace gets defined, though.

--> Let's consider for automatic configure for workspace subscription once user register a new app and workspace using Yaml.



 Comments   
Comment by Zdenek Skodik [ 03/Jan/19 ]

In the context of publishing modules all workspaces are enabled by default for any configured receiver.

Generated at Mon Feb 12 00:37:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.