Consider making the cloneAs config action optionally fail if the clone already exists

Created on 23 October 2024, 6 months ago

Problem/Motivation

Right now, the cloneAs config action will respect existing entities with the same ID as the clone, and leave them alone. We should consider making this configurable, so that the action can fail if the clone already exists.

Possible syntax:

node.type.page:
  # If the `article` content type already exists, leave it alone.
  cloneAs: article
user.role.authenticated:
  # Fail if the `special_sauce` role already exists.
  cloneAs:
    id: special_sauce
    fail_if_exists: true
✨ Feature request
Status

Active

Version

11.0 πŸ”₯

Component

recipe system

Created by

πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024