Skip to content

Ability to remove content definitions via recipe #7515

Description

@bedegaming-aleksej

As a content manager, I want to be able to remove content definitions I have added by running a recipe. This will allow more flexibility when deploying content changes.

At present, there is a way to add content definitions and content itself through recipes. There is also functionality allowing to remove actual content via recipes using RemoveContentStep. However, there is no support for removal of content definitions apart from doing that through migrations. Since those could be added through recipes, it would be nice to be able to remove them by the same means.

Acceptance criteria

  • Content definitions can be removed by using RemoveContentDefinition step
  • RemoveContentDefinition step shall support removal of one or multiple Types and / or Parts definitions at a time
  • RemoveContentDefinition step shall be structured in the same way as RemoveContent step:
<RemoveContentDefinition>
  <Types>
    <{TypeName}/>
    {other types}
  </Types>
  <Parts>
    <{PartName}/>
    {other parts}
  </Parts>
</RemoveContentDefinition>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions