Skip to content

Commit

Permalink
🐛 Add excludeFor example for questionnaire (#1684)
Browse files Browse the repository at this point in the history
Resolves https://issues.redhat.com/browse/MTA-1965

Signed-off-by: ibolton336 <ibolton@redhat.com>
  • Loading branch information
ibolton336 authored Feb 14, 2024
1 parent 046ccf6 commit 6217116
Showing 1 changed file with 24 additions and 1 deletion.
25 changes: 24 additions & 1 deletion client/public/templates/questionnaire-template.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,6 @@ sections:
risk: unknown
rationale: Lack of clarity on architecture can lead to unplanned issues.
mitigation: Conduct an architectural review.

- order: 3
text: Is your application's data storage cloud-optimized?
explanation: Evaluate if the data storage solution is optimized for cloud usage.
Expand All @@ -81,6 +80,30 @@ sections:
risk: yellow
rationale: Hybrid solutions may have integration complexities.
mitigation: Evaluate and optimize cloud integration points.
- order: 4
text: Are you currently using any form of container orchestration?
explanation: Determine if the application utilizes container orchestration tools like Kubernetes, Docker Swarm, etc.
excludeFor:
- category: Deployment
tag: Serverless
- category: Architecture
tag: Monolith
answers:
- order: 1
text: Kubernetes
risk: green
rationale: Kubernetes is a robust orchestrator for container management.
mitigation: Ensure Kubernetes configurations are optimized for cloud.
- order: 2
text: Docker Swarm
risk: green
rationale: Docker Swarm provides a simpler, yet effective, orchestration.
mitigation: Validate that Docker Swarm meets all cloud scalability requirements.
- order: 3
text: No Container Orchestration
risk: yellow
rationale: Lack of container orchestration can hinder cloud adaptability.
mitigation: Explore container orchestration options for better cloud integration.
thresholds:
red: 1
yellow: 30
Expand Down

0 comments on commit 6217116

Please sign in to comment.