Feature Overview
Parent feature to capture engineering tasks for product inclusion and tracking.
Full details are here: https://docs.google.com/document/d/1YOJoC7VORRLHo-w-GCkUSgwEhITkGOPRPc7mCVVmoJo/edit?tab=t.0
Goals
- Make MCE the primary location for Maestro in ACM (and remove reliance and deprecate the previous maestro add-on)
- Allow customers to use Maestro with different protocols
- gRPC as default
- Kafka for large scale requirements.
- Bring gRPC capabilities into ACM to support this
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
Requirement | Notes | isMvp? |
---|---|---|
CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- Search needs a way to handle its 🚨 CNV ‼️ results
https://issues.redhat.com/browse/ACM-21995
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
- blocks
-
ACM-21413 Real-Time Data Streaming for Search API
-
- In Progress
-
- depends on
-
ACM-13223 [DP] Maestro ACM adoption
-
- In Progress
-
- is depended on by
-
ACM-21413 Real-Time Data Streaming for Search API
-
- In Progress
-
- is Informed by
-
ACM-21995 Search streaming implementation alternatives
-
- Closed
-
- relates to
-
ACM-13223 [DP] Maestro ACM adoption
-
- In Progress
-
-
ACM-21245 Investigate Interface Layer for Argo CD Agent to Support Maestro Integration
-
- Backlog
-
-
ACM-12359 Make maestro addon as TP feature
-
- Closed
-