Problem/Motivation

For a distributed team, the feature bundle configuration is a key workflow requirement in collaboratively editing features.

Proposed resolution

Add a configurable option to the profile assignment plugin to add the bundle to the profile. Also (a) remove Features bundle from the default settings on the exclude plugin, and add it to the default settings of the optional plugin (to avoid creating a dependency in the install profile on Features).

Remaining tasks

User interface changes

API changes

Data model changes

Comments

nedjo created an issue. See original summary.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
CreditAttribution: bkosborne at Princeton University commented
Category: Feature request » Bug report

I wonder if this is related to some seriously confusing behavior I'm seeing, and if so, this seems like a bug.

I have a features bundle setup so it creates a profile. I loaded up a bunch of config into this profile, including the features bundle config, with the idea that all the settings I've created for the bundle config will be setup when a site installed with this install profile. I modified the "Exclude" package to uncheck "Features Bundle", so that it actually gets written to my profile.

I write out my profile, and the features.bundle.my_bundle.yml file is there in the install profile's config/intall folder, and it has the correct settings.

Here's the problem. After installing a site with the profile, the bundle config is created, but it has all default settings! So the bundle config that's part of my install profile was ignored. Why is that? Is the expectation that I would store the bundle config as part of a module, and not the install profile?

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo at Drutopia commented
Category: Bug report » Feature request
Status: Active » Closed (duplicate)

@bkosborne

Thanks for noting that issue. It sounds like a bug. Please file a new issue.

I'm closing this issue as a duplicate of #2621750: New 'devel' assignment plugin to package bundle. That issue outlines a better approach. For one thing, putting a bundle in config/optional as proposed in this issue doesn't work, since Features creates the bundle automatically (cloning the default bundle) and the optional config is therefore never installed.