-
Notifications
You must be signed in to change notification settings - Fork 875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
align workload/trait definition schema with v0.2.2 spec #1117
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1117 +/- ##
==========================================
- Coverage 53.74% 52.04% -1.70%
==========================================
Files 70 72 +2
Lines 5975 6244 +269
==========================================
+ Hits 3211 3250 +39
- Misses 2404 2634 +230
Partials 360 360
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
// Schematic defines the encapsulation of this capability(workload/trait/scope), | ||
// the encapsulation can be defined in different ways, e.g. CUE/HCL(terraform)/KUBE(K8s Object)/HELM, etc... | ||
type Schematic struct { | ||
CUE *CUE `json:"cue,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some discussions about using a plug-in model instead of hardcode each schematic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The agreement is we keep it as is until another new schematic type besides CUE, Helm, Kube, ARM comes in.
fix #976
align with oam-dev/spec#443