[ENG-3857] Refactor: Providerinfo subscribe support config

[jlimatampersand]

These registration, maintenance, postprocess configs were in server repo, but we should move to provider info.

[linear]

ENG-3857 Refactor Subscribe Support in ProviderInfo

[laurenzlong]

SubscribeSupportConfig is not the best name because both support and config are confusing - support is used to track which features we support, config is about information provided by consumers, this is neither.

[graphite-app]

Schema name mismatch: The schema is defined as SubscribeRequirements but line 586 references SubscribeSupportConfig. This will cause schema resolution to fail.

# Change from:
SubscribeRequirements:
  title: Subscribe Action Requirements
  
# To:
SubscribeSupportConfig:
  title: Subscribe Support Config

The schema name must match the $ref target at line 586, or the reference must be updated to point to SubscribeRequirements. Based on the generated JSON files using SubscribeSupportConfig, the schema should be renamed to SubscribeSupportConfig.

Suggested change

	SubscribeRequirements:
	title: Subscribe Action Requirements
	type: object
	description: Declares which auxiliary steps a provider requires to support subscriptions, beyond the per-object subscribe call itself.
	properties:
	registration:
	type: boolean
	description: >-
	Whether the provider requires a one-time registration step that is shared across all subscribed objects.
	The subscribe method is object-scoped, so if a separate API call is needed beyond per-object configuration
	(e.g., registering a single webhook/endpoint that all object subscriptions hang off of), registration is required.
	maintenance:
	type: boolean
	description: >-
	Whether the subscription requires periodic maintenance. Some providers expire subscriptions/watches after
	a fixed TTL, so the subscription must be renewed on a schedule to remain active.
	postProcess:
	type: boolean
	description: >-
	Whether subscribing requires a third-party setup step that the connector instance itself cannot perform.
	Examples: Salesforce requires AWS EventBridge configuration; Gmail requires a Google Pub/Sub topic to be
	configured. Any configuration that must happen outside the connector falls into post-process.
	SubscribeSupportConfig:
	title: Subscribe Support Config
	type: object
	description: Declares which auxiliary steps a provider requires to support subscriptions, beyond the per-object subscribe call itself.
	properties:
	registration:
	type: boolean
	description: >-
	Whether the provider requires a one-time registration step that is shared across all subscribed objects.
	The subscribe method is object-scoped, so if a separate API call is needed beyond per-object configuration
	(e.g., registering a single webhook/endpoint that all object subscriptions hang off of), registration is required.
	maintenance:
	type: boolean
	description: >-
	Whether the subscription requires periodic maintenance. Some providers expire subscriptions/watches after
	a fixed TTL, so the subscription must be renewed on a schedule to remain active.
	postProcess:
	type: boolean
	description: >-
	Whether subscribing requires a third-party setup step that the connector instance itself cannot perform.
	Examples: Salesforce requires AWS EventBridge configuration; Gmail requires a Google Pub/Sub topic to be
	configured. Any configuration that must happen outside the connector falls into post-process.

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.