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.

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

Matomo 5.2.2 Upgrade #21

Merged
merged 3 commits into from
Feb 5, 2025
Merged

Matomo 5.2.2 Upgrade #21

merged 3 commits into from
Feb 5, 2025

Conversation

cabutlermit
Copy link
Contributor

@cabutlermit cabutlermit commented Feb 4, 2025

What does this PR do?

Upgrades our Matomo ECS service in AWS to version 5.2.2.

Helpful background context

UXWS requested an upgrade to our Matomo instance. As part of the initial testing in Dev1, not only are we upgrading the version of Matomo, we are also upgrading the versions of the two plugins and making a minor change to the config file.

How can a reviewer manually see the effects of these changes?

The new version is currently running in Dev1 at Dev1-Matomo.

Includes new or updated dependencies?

NO

What are the relevant tickets?

Developer

  • All new ENV is documented in README (or there is none)
  • Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

  • The commit message is clear and follows our guidelines
    (not just this pull request message)
  • There are appropriate tests covering any new functionality
  • The documentation has been updated or is unnecessary
  • The changes have been verified
  • New dependencies are appropriate or there were no changes

Why these changes are being introduced:
UXWS requested an upgrade to the latest version of Matomo. As part of
the initial testing of the upgrade in Dev1, it was noted that an
additional PlugIn appeared in the config.ini.php file.

How this addresses that need:
* Upgrade the Docker source from 5.1.2 to 5.2.2
* Update the config.ini.php file to include the newly listed
FeatureFlags PlugIn
* Update the config.ini.php to include the collation detail

Side effects of this change:
None.

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/INFRA-506
* https://mitlibraries.atlassian.net/browse/INFRA-499
* https://mitlibraries.atlassian.net/browse/INFRA-495
Why these changes are being introduced:
During the testing and verification of the new 5.2.2 version of Matomo,
it was discovered that there were newer versions of the two extra
PlugIns that we use. At the same time, we cleared out some old copies
of plugins from this repository.

How this addresses that need:
* Add new CustomVariables 5.0.4 plugin folder
* Add new EnvironmentVariables 5.0.3 plugin folder
* Remove extra older plugin folders for both CustomVariables and
EnvironmentVariables plugins

Side effects of this change:
None.

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/INFRA-506
@cabutlermit cabutlermit requested a review from a team February 4, 2025 21:57
@cabutlermit
Copy link
Contributor Author

Actually --- hold off on reviewing! Just remembered that I need to update the README. I'll push updates first thing tomorrow morning.

Why these changes are being introduced:
All Infra-related repositories need a CODEOWNERS file and additional
sections in the README to ensure that the links between repositories
are clearly documented.

How this addresses that need:
* Create a CODEOWNERS file
* Add a Related Assets section and a Maintainers section to the README

Side effects of this change:
None.
@cabutlermit
Copy link
Contributor Author

@MITLibraries/infraeng-terraform-reviewers

Documentation updates are pushed. Now it's ready for review.

Copy link
Contributor

@tim-rix tim-rix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks OK to me.

@cabutlermit cabutlermit merged commit f0ee3fd into main Feb 5, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants