|
CONFIGURATION_ACTIVESTORE_OVERRIDDEN |
./configuration.module |
A bit flag used to let us know if a configuration was overridden as a result
of changing the activestore directly. (config changes via the UI) |
9 |
1 |
|
CONFIGURATION_CONFLICT |
./configuration.module |
Both activestore and datastore have a changed. We have a conflict. |
1 |
1 |
|
CONFIGURATION_DATASTORE_ONLY |
./configuration.module |
A bit flag used to let us know if a configuration is only in the datastore. |
10 |
1 |
|
CONFIGURATION_DATASTORE_OVERRIDDEN |
./configuration.module |
A bit flag used to let us know if a configuration was overridden as a result
of changing the datastore directly. |
9 |
1 |
|
CONFIGURATION_DEFAULTS_CUSTOM |
./configuration.module |
Components with this 'default_file' flag must specify a filename for their
exports. Additionally a stub will NOT be written to 'MODULENAME.features.inc'
allowing the file to be included directly by the implementing module. |
2 |
1 |
|
CONFIGURATION_DEFAULTS_INCLUDED |
./configuration.module |
Components with this 'default_file' flag will have exports written to a
defaults based on the component name like 'MODULENAME.features.COMPONENT-NAME.inc'.
Any callers to this component's defaults hook must… |
11 |
1 |
|
CONFIGURATION_DEFAULTS_INCLUDED_COMMON |
./configuration.module |
Components with this 'default_file' flag will have exports written to the
common defaults file 'MODULENAME.features.inc'. This is the default
behavior. |
|
1 |
|
CONFIGURATION_DELETE |
./configuration.module |
If a configuration no longer exists in the active store and still exists in config tracking. |
3 |
1 |
|
CONFIGURATION_DEPENDENCY_REQUIRED |
./configuration.module |
If a configuration requires a dependency that isn't installed. |
|
1 |
|
CONFIGURATION_DISABLED |
./configuration.module |
|
|
1 |
|
CONFIGURATION_DUPLICATES_ALLOWED |
./configuration.module |
Components with this 'duplicates' flag are allowed to have multiple features
provide the same component key in their info files. |
1 |
1 |
|
CONFIGURATION_DUPLICATES_CONFLICT |
./configuration.module |
Components with this 'duplicates' flag may not have multiple features provide the
same component key in their info files. This is the default behavior. |
|
1 |
|
CONFIGURATION_IN_SYNC |
./configuration.module |
A bit flag used to let us know if a configuration is the same in both the
activestore and the datastore. |
13 |
1 |
|
CONFIGURATION_MODULE_DISABLED |
./configuration.module |
|
|
1 |
|
CONFIGURATION_MODULE_ENABLED |
./configuration.module |
|
|
1 |
|
CONFIGURATION_MODULE_MISSING |
./configuration.module |
|
|
1 |
|
CONFIGURATION_NEEDS_REVIEW |
./configuration.module |
|
1 |
1 |
|
CONFIGURATION_OVERRIDDEN |
./configuration.module |
A bit flag used to let us know if a configuration was overridden. |
1 |
1 |
|
CONFIGURATION_REBUILDABLE |
./configuration.module |
|
1 |
1 |
|
CONFIGURATION_REBUILDING |
./configuration.module |
|
1 |
1 |
|
CONFIGURATION_SEMAPHORE_TIMEOUT |
./configuration.module |
|
1 |
1 |
|
CONFIGURATION_TRACKED_DATASTORE_ONLY |
./configuration.module |
A bit flag used to let us know if a configuration is only in the datastore
and is also being tracked in config.export. |
13 |
1 |
