* remove limits we do not listen to anymore
* add back boards property for focalboard project compatibility
* remove boards cards as paid feature
* remove lingering unlimited integrations paid feature
https://mattermost.atlassian.net/browse/MM-49485
```release-note
Boards will be served as an in-built product from
within Mattermost server instead of a plugin.
If you want to disable this, please set the
MM_FEATUREFLAGS_BoardsProduct env var to "false" (without
the quotes).
In this mode, the boards plugin will remain disabled.
```
* [MM-47648] Handler for check if a subscription is expandable
* Mock cloud regenerate
* PR Webapp test purpose only
* [MM-47648] Refactor and tests for expand stats for a subscription
* Fix typos
* style fix
* has to be revert
* CWS URL to Spinwick
* new spinwick url
* target portal test
* Generate token instead of send licenseId
* Rename
* Rename methods
* Revert public key and cws url
Co-authored-by: Mattermod <mattermod@users.noreply.github.com>
* Add restore_group permission
* Fix tests failing due to new permission in groups
* Add new migration to add custom_group_restore permission
* Add mock for new migration function
* Fix tests
Co-authored-by: Mattermod <mattermod@users.noreply.github.com>
* Implement Auditable Function for Patch Post Endpoint
* Call auditable explicitly for patchPost patch parameter
* Delete audit-config.json
* Include HasReactions in Audit Log Entry for Patch
* Self-hosted admins can purchase licenses in-app when `ServiceSettings,SelfHostedPurchase` is true (the default)
* Content Security Policy enables loading assets from `js.stripe.com/v3` when `ServiceSettings.SelfHostedPurchase` is true (the default).
* Add `hosted_customer` API subpath
* Add status of SelfHostedPurchase to telemetry config report.
* Support showing admins self-hosted invoices when `ServiceSettings.SelfHostedPurchase` is true (the default)
Co-authored-by: Conor Macpherson <116016004+ConorMacpherson@users.noreply.github.com>
Although this isn't the root cause for the panic in the sentry crash,
this is indeed a bug and will cause a crash in the exact same way.
I have looked at other possibilities and I don't see any other
way for model.ChannelMembers to panic during json marshaling.
Other sentry crashes are there for ths customer and they point
to data corruption which indicates there is something funky going on.
Nevertheless, this is a valid bug and should be fixed.
https://mattermost.atlassian.net/browse/MM-48553
```release-note
NONE
```
* Respond with bad requests for wrong query parameters in roles
* Revert "Respond with bad requests for wrong query parameters in roles"
This reverts commit d8374d94e0b1f61ad445127010f9780475c48d1a.
* Add GetUser client function to query with channel_id and roles
* Return bad parameters error on invalid roles
* Make client function generic, lint fixes
* i18n strings addition
* Validate 'role', add stricter check for comma separated roles
