Tech Debt: Make triggers belong to Operations
Bug #1295328 reported by
Adrian Otto
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Solum |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Our plan to use a temporary assembly resource to store the trigger_id for an app violates the concept that Assembly resources represent running applications. Triggers should instead be connected to an Operation resources that are related to Component resources that represent a DU within an Assembly.
The initial Operation resource does not initially need to be associated with a Component. Once the Du is created, the Component resource may be created to represent it, and the Operation resource (with the trigger_id on it) may then be associated with the Component that is part of a new Assembly.
Revision history for this message
| Adrian Otto (aotto) wrote | #1 |
| summary: |
- Make triggers belong to Components + Make triggers belong to Operations |
Revision history for this message
| Angus Salkeld (asalkeld) wrote Re: Make triggers belong to Operations | #2 |
| Changed in solum: | |
| milestone: | none → milestone-2 |
| summary: |
- Make triggers belong to Operations + Tech Debt: Make triggers belong to Operations |
| Changed in solum: | |
| status: | New → Triaged |
| tags: | added: tech-debt |
| Changed in solum: | |
| milestone: | 2014.1.2 → juno-1 |
| Changed in solum: | |
| milestone: | juno-1 → juno-2 |
Revision history for this message
| Adrian Otto (aotto) wrote | #3 |
| Changed in solum: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The current implementation also does not work for cases where an assembly may contain multiple DU's, each represented by a separate code repository. We want to be able to trigger the rebuild of DU's individually wihtout requiring the full re-creation of the assembly that contains them.