"/**/*" behavior is unusual, effectively ".*$" rather than "/.*$"

[dagood]

The behavior of /**/* is defined here:

versions/Maestro/src/Microsoft.DotNet.Maestro.WebApi/Models/SubscriptionsModel.cs

Lines 89 to 93 in 1c00f95

	if (path.EndsWith("/**/*", StringComparison.OrdinalIgnoreCase))
	{
	string rootPath = path.Substring(0, path.Length - 5);
	return modifiedFile.FullPath.StartsWith(rootPath, StringComparison.OrdinalIgnoreCase);
	}

This means /**/* matches file changes where the url starts with everything up to the /, exclusive. For example, release/3.0/**/* will match release/3.0/foo/bar but also, unexpectedly, release/3.0.5/foo/bar.

To work around the issue and make the pattern behave as expected, you must instead use //**/*. release/3.0//**/* will match release/3.0/foo/bar but not release/3.0.5/foo/bar.

This could be fixed. subscriptions.json is the only place this behavior is depended on, and it lives in this repo. A complication is is that the service reads subscriptions.json live, from GitHub, but the service must be manually deployed. (The service is deployed extremely rarely.)

---

Note that general glob patterns are not generally supported. /**/* is detected specifically. See #207 proposing more general support, or switching over to regex.