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

Support merge offline packages #814

Closed
lucklove opened this issue Sep 25, 2020 · 0 comments
Closed

Support merge offline packages #814

lucklove opened this issue Sep 25, 2020 · 0 comments
Assignees
@lucklove
Labels
priority/P1 Indicates that the priority of a issue is high. status/TODO Categorizes issue as we will do it. type/feature-request Categorizes issue as related to a new feature.
Milestone
v1.3.0

Comments

@lucklove
Copy link
Member

Feature Request

Is your feature request related to a problem? Please describe:

At current, if the user use a offline package to deploy his cluster, when he want to upgrade it to another version, or he want to deploy a cluster with a different version. He must switch the mirror to the right offline package via the command tiup mirror set.

Describe the feature you'd like:

There should be a way to merge two different offline package to a bigger package which contains all the components from both offline packages, so that we don't need to execute tiup mirror set to manager different version cluster.
@lucklove lucklove added the type/feature-request Categorizes issue as related to a new feature. label Sep 25, 2020
@lucklove lucklove added the status/TODO Categorizes issue as we will do it. label Sep 25, 2020
@lucklove lucklove added this to the v1.3.0 milestone Sep 25, 2020
@lucklove lucklove added the priority/P1 Indicates that the priority of a issue is high. label Sep 25, 2020
@lucklove lucklove self-assigned this Sep 25, 2020
@lucklove lucklove mentioned this issue Oct 22, 2020
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lucklove lucklove

Labels
priority/P1 Indicates that the priority of a issue is high. status/TODO Categorizes issue as we will do it. type/feature-request Categorizes issue as related to a new feature.
Projects
None yet
Milestone
v1.3.0
Development

No branches or pull requests
1 participant
@lucklove