-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat(caas): backport from caas #42
Conversation
8c7d87a
to
0c65232
Compare
/test-examples |
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.
Added the initial feedback
Signed-off-by: Christopher Haar <[email protected]>
458adc9
to
df2b595
Compare
/test-examples |
Signed-off-by: Christopher Haar <[email protected]>
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.
Can we make git mv package/cluster/composition.yaml apis/cluster/composition.yaml
so the actual diff will be visible? For all the moved files involved.
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.
i will split this PR for better visibility: first: #43
followup via: #44 |
Description of your changes
Fixes #
I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR, as appropriate.How has this code been tested
uptest