Changelog: VIP MU plugins [Production]

The warnings were already reviewed previously and deemed false positive in this case.

However, we updated the implementation here to silence/resolve the warnings.

https://github.com/Automattic/vip-go-mu-plugins/pull/1920

As part of improving our SDLC process, we’re going to require proposals for feature additions / significant feature alterations. This will allow us to ensure that features and significant feature alterations deliver much more value to our platform by being properly planned out, executed, and released.

https://github.com/Automattic/vip-go-mu-plugins/pull/1908

#mu-plugins

We keep working in the Site Details functionality, that will allow us to have up to date details about sites, such as the list of plugins and their versions, whether VIP Search is enabled, Jetpack connection status…

While the final implementation is still in progress, we are now storing site details in a temporary location in logstash, so that we can start using this data as soon as possible. One example is finding all sites that are running a certain version of a plugin, to prepare for an upgrade to a newer version.

https://github.com/Automattic/vip-go-mu-plugins/pull/1924

#mu-plugins #site-details

We keep working in the Site Details functionality, that will allow us to have up to date details about sites, such as the list of plugins and their versions, whether VIP Search is enabled, Jetpack connection status…

This adds some more fields, namely the information about Jetpack (version, active status, Jetpack id, active modules). In the future, all these will be stored and be accessible to run actions on them. E.g, easily find all sites that have a certain old Jetpack version that needs upgrading.

https://github.com/Automattic/vip-go-mu-plugins/pull/1923

#mu-plugins #site-details

We have updated stats keys allowing us to better track usage for Cache Manager functionality.

https://github.com/Automattic/vip-go-mu-plugins/pull/1922

#mu-plugins

The warnings were already reviewed previously and deemed false positive in this case.

However, we updated the implementation here to silence/resolve the warnings.

https://github.com/Automattic/vip-go-mu-plugins/pull/1919

We’ve fixed bug which caused the replaceIPAllowListMutation to not work correctly when passed an empty array. The fix now correctly disables the IP Allow List from the environment when given an empty array.

Example query:

mutation replaceIPAllowListMutation($input: AppEnvironmentIPAllowListInput) {
	replaceIPAllowList(input: $input) {
		app {
			id
		}
		ips
	}
}

With variables:

{
	"input": {
		"id": 999999,
		"environmentId": 999999,
		"ips": []
	}
}

#cloud-api #ip-allow-list

We’ve updated our skeleton repo to use Twenty Twenty One v1.1 which includes various bug fixes. All new applications will have their repos generated with this new version. Existing applications can update their version by downloading the new version from the WordPress.org Theme Directory.

https://github.com/Automattic/vip-go-skeleton/pull/62

#skeleton

To assist with debugging VIP Search related issues, we need an easy way to determine if rate limiting is currently in effect for queries or indexing operations. The easiest way to accomplish this right now is by logging when rate limiting starts to logstash.

https://github.com/Automattic/vip-go-mu-plugins/pull/1916

In order to provide stable and robust index versioning for our search offering, we need to be able to detect and heal any issues with the versioning data.

This feature is the first step towards that goal. It detects index versioning issues and logs them without performing any actions so we can identify any potential issues before rolling this out to all VIP Search users.

There will be an additional change in the future to allow this to run for real once we’ve verified everything operates as we intend.

https://github.com/Automattic/vip-go-mu-plugins/pull/1881

There was an extraneous comma added in Feature: Flush Cache for Page. This didn’t affect any of our environments. The issue only presents itself in earlier PHP versions and only caused some issues when running certain tests locally with phpunit-docker.sh. This comma was removed to address this issue and won’t affect anything else.

https://github.com/Automattic/vip-go-mu-plugins/pull/1915

Updated Test jQuery Updates to the latest upstream version to bring in support for WordPress 5.7 and various minor improvements / bugfixes.

Note We are on 2.0.x because have modified the plugin. The current latest 2.0 release doesn’t operate as expected on read-only file systems due to capability check changes. An issue have been opened here.

https://github.com/Automattic/vip-go-mu-plugins/pull/1901

Updated old documentation URLs and WordPress.com VIP references in code comments and some customer-facing strings.

https://github.com/Automattic/vip-go-mu-plugins/pull/1911

Allow any environment that is correctly configured to run the concatenation plugin to do so and use the same logic as VIPs environments.

https://github.com/Automattic/vip-go-mu-plugins/pull/1913

Previously VIP Search registered actions to handle deleted content during plugins_loaded, but this is too early as some Indexables may not have been registered yet. VIP Search sets up Features (and their Indexables) on init, which comes later.

https://github.com/Automattic/vip-go-mu-plugins/pull/1903

Starting today, users that have manage_options capability will be able to flush the page cache for any page and its related style and script assets. Look for “Flush Cache for Page” button in the admin bar.

https://github.com/Automattic/vip-go-mu-plugins/pull/1880

Learn more in our Lobby post.

#mu-plugins

Core WordPress tests are already validated as running successfully as part of the WordPress release process. Running them without including vip-go-mu-plugins on every change to vip-go-mu-plugins isn’t necessary.

We will continue to run the WordPress core test jobs in CircleCI that include vip-go-mu-plugins on every change to ensure changes work as expected with WordPress core.

https://github.com/Automattic/vip-go-mu-plugins/pull/1910

add_role can lead to database writes which, when called on init, can trigger on the frontend. That is not ideal as it can cause performance problems. It can also lead to undesirable circumstances with other roles being removed if there are intermittent database issues.

We still trigger our upgrade routine on admin_init so new installs still get the VIP Support roles added correctly.

https://github.com/Automattic/vip-go-mu-plugins/pull/1912

We have a couple of CircleCI jobs that run core tests with vip-go-mu-plugins attached for each submitted change. Sometimes vip-go-mu-plugins ends up changing assertions in a core test and those tests need to be excluded since we know they will fail 100% of the time.

https://github.com/Automattic/vip-go-mu-plugins/pull/1909

We need to keep the changelog up to date so that everyone can be informed of changes to our platform. We’re adding processes in to make that a reality and having a reminder in the PR template is a part of facilitating those processes.

https://github.com/Automattic/vip-go-mu-plugins/pull/1907