-
Notifications
You must be signed in to change notification settings - Fork 131
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
PMM-13031: Upgrades PMM 2 client with PMM 3 client. #3182
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## v3 #3182 +/- ##
==========================================
- Coverage 44.61% 44.58% -0.04%
==========================================
Files 357 357
Lines 35711 35711
==========================================
- Hits 15933 15921 -12
- Misses 18154 18166 +12
Partials 1624 1624
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
4b06c24
to
6a7efaf
Compare
rmdir /usr/local/percona/pmm2/config | ||
fi | ||
|
||
if [ -d /usr/local/percona/pmm2 ] && [ ! "$(ls -A /usr/local/percona/pmm2)" ]; then |
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.
if I got it right we remove this directory only if it's empty, right?
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.
@BupycHuk Yes you are right.
This commit enables PMM 3 client RPM and Debian packages to upgrade existing PMM 2 client installation and migrate existing pmm-agent.yaml file from PMM 2 to PMM 3 installation directory. It also keeps the pmm-agent.yaml file of PMM client 3 as pmm-agent.yaml.new.
On successful upgrade if pmm2 installation directory is empty then it will be removed. A non empty directory will not be deleted.