Add drush command to set a feature status

Created on 19 January 2021, almost 4 years ago
Updated 14 October 2023, about 1 year ago

Problem/Motivation

To integrate feature_toggle into automated setups, e.g. CI/CD it would be great if we can set a feature toggle via command line, preferably via drush

Proposed resolution

Add a custom drush command which allows to set the status of a named feature toggle.

Remaining tasks

*

User interface changes

none

API changes

none

Data model changes

none

Feature request
Status

RTBC

Version

2.0

Component

Code

Created by

🇩🇪Germany stmh

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.1.x + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    5 pass
  • Status changed to RTBC about 1 year ago
  • 🇳🇱Netherlands eelkeblok Netherlands 🇳🇱

    It's a bit confusing, Drupal.org told me that the MR was ready to merge, but GitLab said there was a problem. It may have had to do with Drupal.org reporting the target to be 8.x-1.x while GitLab has 2.0.x as its target (btw, I would suggest to use 2.1 as the release version once this is merged, since this is a new feature). Either way, I merged 2.0.x into the MR branch, which seems to have satisfied GitLab. Maintainer should have the option to merge right from the issue, which will squash the whole thing down into a single commit on the current 2.0.x branch (again. consider making a 2.1.x branch and changing the MR target before doing so).

    Would love to see this in the module, would make it even more useful.

Production build 0.71.5 2024