-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
Feature Overview
Blueprints currently support multiple image types, but this isn't possible with image mode and makes things much more complicated when presenting a user with customizations that are only supported by a subset of selected types. Data shows that a small minority of users actually use multiple image types in a single blueprint.
Goals
Requirements
| requirement | Notes | Is Mvp? |
| Creation wizard allows selecting only one image type (target environment) per blueprint. | Y | |
| Edit wizard loads blueprints with a single image type; multi-type blueprints are handled via migration flow (see Migration) | Y | |
| Customization steps show only options supported by the selected image type | Y | |
| API (create/update blueprint) and backend accept/enforce at most one image request per blueprint. | Y | |
| Migration path for existing blueprints that have multiple image_requests | Y | |
| Import blueprint (file): if imported blueprint has multiple image types, apply same migration behavior (e.g. pick one type or create one blueprint per type) | Y | |
| Clone blueprint to change image type | Maybe? |
Non-Functional Requirements
< Please take a look at this nice guide talking about NFRs: Top 10 Architecture Characteristics/Non-Functional Requirements with Cheatsheet. Non-Functional Requirements (NFR)s should be considered when planning and are considered Acceptance Criteria for this Feature. >
Use Cases (User Experience & Workflow)
The user workflow will be the same as today, only a single image type is selectable.
The migration path needs to be discussed
How will a user achieve multiple image types? We don't have a 'clone' function today, should we?
Customer Considerations
Customers that use a blueprint with more than one image type will need to migrate (or have their blueprints migrated) prior to building an image from the existing blueprint.
Customer Information/Supportability
Currently about 12% of blueprint contain more than one image type.
Documentation Considerations
- Docs will need to be updated to explain to users how to achieve this.