mirror of
https://gh.wpcy.net/https://github.com/discourse/discourse.git
synced 2026-05-04 05:09:20 +08:00
## Summary Patreon API v1 has been deprecated for years and the Patreon team has requested we migrate to v2 (see https://meta.discourse.org/t/upgrade-patreon-discourse-plugin-to-api-v2/386701). Since hundreds of existing customers have v1 OAuth clients, this PR supports **both versions simultaneously** via an adapter pattern, controlled by a new `patreon_api_version` site setting (defaults to `"1"` so no one breaks on upgrade). ### What changed - **Adapter pattern**: `Patreon::ApiVersion::V1` and `ApiVersion::V2` modules with identical interfaces for endpoints, response parsing, and OAuth config. `ApiVersion.current` routes based on the site setting. - **v2 API support**: campaigns endpoint returns tiers (not rewards), members fetched separately with cursor-based pagination, v2 identity endpoint with explicit field selection, v2 OAuth scopes - **Webhooks accept both formats**: payload version detected from `data.type` (`"pledge"` → v1, `"member"` → v2), regardless of the site setting - **Admin deprecation notice**: `ProblemCheck::PatreonApiV1Deprecated` warns on the dashboard when still using v1 - **Shared logic unchanged**: rate limiting, PluginStore, group sync, admin UI all version-agnostic - Also fixes pre-existing flaky seed/campaign spec failures ### Migration path for existing users 1. Admin sees deprecation warning on dashboard 2. Create a new v2 OAuth client at https://www.patreon.com/portal/registration/register-clients 3. Update credentials in site settings 4. Switch `patreon_api_version` to `"2"` 5. Creator re-authenticates via Patreon login to get v2-scoped tokens 6. Trigger a manual data sync from the Patreon admin panel ### Future v1 removal When ready to drop v1: delete `lib/api_version/v1.rb`, the problem check, the site setting, v1 fixtures, and v1 test contexts — one clean cut. ## Test plan - [x] All 41 plugin specs pass (both v1 and v2 contexts) - [x] Lint passes on all changed files - [x] Zeitwerk reload passes (`bin/rails runner "Rails.application.reloader.reload!"`) - [x] Manual testing with a real Patreon v2 OAuth client
31 lines
880 B
Ruby
31 lines
880 B
Ruby
# frozen_string_literal: true
|
|
|
|
require "json"
|
|
|
|
module Patreon
|
|
class Tokens
|
|
def self.update!
|
|
adapter = ApiVersion.current
|
|
conn = Faraday.new(url: adapter.token_base_url)
|
|
|
|
response =
|
|
conn.post(
|
|
adapter.token_path,
|
|
grant_type: "refresh_token",
|
|
refresh_token: SiteSetting.patreon_creator_refresh_token,
|
|
client_id: SiteSetting.patreon_client_id,
|
|
client_secret: SiteSetting.patreon_client_secret,
|
|
)
|
|
|
|
if response.status == 200
|
|
tokens = JSON.parse response.body
|
|
SiteSetting.patreon_creator_access_token = tokens["access_token"]
|
|
SiteSetting.patreon_creator_refresh_token = tokens["refresh_token"]
|
|
else
|
|
Rails.logger.warn(
|
|
"Patreon token refresh failed with status: #{response.status}.\n\n #{response.body}",
|
|
)
|
|
end
|
|
end
|
|
end
|
|
end
|