What operations do you want to perform on a recipe?

[jenlampton]

I'm working on setting up the actionable items for recipes, and this is what I have so far:

• Enable - enables the module, imports the config.
• View - Lists all the individual files in a recipe
  • each one of these could offer a "delete me" link (WARN IF CONTENT WILL BE LOST)
• Revert - Re-imports the config, removing any changes made to the local copy.

These are things I'm not sure would be valuable:

• Remove - Removes all the config files from this recipe, at once. (I don't know if this is a good idea... thoughts?)
• Export - Exports the config, and delivers a replacement recipe .zip file.

---

See related: #10 What should we name the operations on recipes?

[izmeez]

Does this issue depend on backdrop/backdrop-issues#5240

[laryn]

This provides an interesting summary of how Recipes are coming out in modern Drupal, for comparison. As far as actions, the summary suggests (not all may be relevant but FYI):

Config Actions:

A powerful feature that provides a more flexible method to manipulate site configuration.
Config actions can be applied globally or to a specific type of config entity.
Config actions are extensible via an API, allowing modules to define their own custom actions.
Common config actions include:

• simple_config_update: Changes a specific setting.
• create_if_not_exists: Creates a config entity if it doesn't already exist; this is critical for maintaining idempotency.
• set_component: Add items like fields to forms or view modes.
• set_third_party_setting: Changes third-party configuration values.
• grant_permissions: Sets permissions for roles.
• add_node_types and add_taxonomy_vocabularies: Applies workflows.
• add_to_all_bundles: Adds a field to content types, etc.
• Block placement configurations.

[oadaeh]

"Inspect" could be something like "Summary" or "View summary".