-
Notifications
You must be signed in to change notification settings - Fork 80
[WIP]Component versioning fix and e2e tests #171
base: master
Are you sure you want to change the base?
[WIP]Component versioning fix and e2e tests #171
Conversation
Signed-off-by: roy wang <seiwy2010@gmail.com>
allow multiple revisions of one component unit test & e2e test Signed-off-by: roy wang <seiwy2010@gmail.com>
Signed-off-by: roy wang <seiwy2010@gmail.com>
Name: revisionName, | ||
Namespace: curComp.Namespace, |
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.
could you help split the namespace in a separated PR as a BUG fix, thanks.
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.
Sure, I will fix it in another PR.
- revisionName: example-component-1 | ||
traits: | ||
- apiversion:core.oam.dev/v1alpha2 | ||
kind: ManualScaler | ||
spec: | ||
replicaCount: 3 | ||
- revisionName: example-component-2 | ||
traits: | ||
- apiversion:core.oam.dev/v1alpha2 | ||
kind: ManualScaler | ||
spec: | ||
replicaCount: 2 |
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.
We are considering it's an anti-pattern, as we could use two different components to do the same thing. Using different revisions of one component seems don't bring any extra bonus.
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.
Okay, before the proposal is ready, let's suspend this PR. But I will separate e2e test covering current versioning mechanism into another PR as well as the fix of #170.
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.
Cool, we can hold this PR until we have a conclusion on that issue
Change: set workload instance name as specified revisionName, if revisionName is provided.