Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handling different minor and major versions of frameworks. #5

Closed
joerg84 opened this issue Nov 26, 2018 · 2 comments
Closed

Handling different minor and major versions of frameworks. #5

joerg84 opened this issue Nov 26, 2018 · 2 comments

Comments

@joerg84
Copy link
Contributor

joerg84 commented Nov 26, 2018

TODO
@runyontr
Copy link
Member

runyontr commented Dec 4, 2018

This can be captured in the InstanceController's predicate.Func. The current logic only idenfies if the FrameworkVerison changes, and calls a single "upgrade" plan. We could expand upon this long to look for minor and major version changes (using SemVer) and call a MajorUpgrade or MinorUpgrade if available, or default to Upgrade if neitehr are specified

@runyontr
Copy link
Member

This is solved by PlanTriggers

alenkacz pushed a commit that referenced this issue Jun 5, 2019
@fabianbaier
Merge pull request #5 from alenkacz/av/cli-improvement-improvement
53ec610 
Read bundles from memory, no local repo. Small fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@runyontr @joerg84