Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

Backend: Remove the concept of a top-level "draft campaign". #10953

@mrnugget

Description

@mrnugget

From RFC 157

Backend

  • Remove the Campaign.publishedAt field (and the concept of a campaign being a draft vs. non-draft/published).
  • Remove the publishCampaign mutation.
  • Add the publishCampaignChangesets mutation: publish all existing campaign changesets that you are permitted to publish.
  • Rename retryCampaign to retryCampaignChangesets
  • Don't publish changesets when campaign is created (user needs to explicitly publish changesets/campaign)

src CLI

Metadata

Metadata

Assignees

Labels

RFC-157Tickets related to RFC 157 - Campaigns authorization modelbatch-changesIssues related to Batch Changesestimate/2droadmapIssue tracking a product-eng roadmap item

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions