Disabling module with config sync and removing with composer

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
3
down vote

favorite

I have an issue disabling modules, I've searched but cannot find something useful:

- Developer A disable module and via composer remove it

- I pull his changes so i run composer install that remove the code, then drush cim to update configuration, but it complains that the module is missing while it's trying to delete its configurations.

What's the right way to do this? I can't import config before running composer install because along the uninstalled module there could be also new modules needed for the configuration import.

asked 2 hours ago

Francesco

182

New contributor

add a commentÂ |Â

up vote
3
down vote

favorite

What's the right way to do this? I can't import config before running composer install because along the uninstalled module there could be also new modules needed for the configuration import.

asked 2 hours ago

Francesco

182

New contributor

add a commentÂ |Â

up vote
3
down vote

favorite

What's the right way to do this? I can't import config before running composer install because along the uninstalled module there could be also new modules needed for the configuration import.

asked 2 hours ago

Francesco

182

New contributor

What's the right way to do this? I can't import config before running composer install because along the uninstalled module there could be also new modules needed for the configuration import.

8 configuration-management composer uninstalling

asked 2 hours ago

Francesco

182

New contributor

asked 2 hours ago

Francesco

182

New contributor

asked 2 hours ago

Francesco

182

New contributor

asked 2 hours ago

Francesco

182

asked 2 hours ago

Francesco

182

New contributor

Francesco is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a commentÂ |Â

2 Answers
2

active

oldest

votes

up vote
2
down vote

accepted

You need two consecutive releases for stuff like that.

First release:

Your colleague uninstalls the module and commits the updated config. But he also needs to ensure that the module needs to get uninstalled via some hook_update_N before the config gets imported in everybody else's setup.

/**
 * Uninstall SOME_MODULE module.
 */
function MYMODULE_update_8001(&$sandbox) 

 Drupal::service('module_installer')->uninstall(['SOME_MODULE']);

Second release:

The module can be removed via Composer.

Order of drush commands for automated deployment?

edited 32 mins ago

answered 1 hour ago

leymannx

5,89042356

Thanks, everything's clear to me! Thanks also for the related question, very intresting!
â€“Â Francesco
1 hour ago

You actually do not require an update hook just to uninstall the module. The configuration management in D8 could be used for it. Added an alternative answer built on top of your. cc @Francesco
â€“Â AjitS
30 mins ago

@AjitS Ã¢Â€Â“ Unsure about that. When drush cim recognizes some missing config, not knowing that some module will be uninstalled from core.extensions.yml later. If I remember it right this can raise an exception.
â€“Â leymannx
11 mins ago

add a commentÂ |Â

up vote
0
down vote

Adding an alternative solution to @leymannx - you will still need two releases. This is taking into consideration your mention of drush cim

First release:

Uninstall the module drush pmu module_name

Export the configuration.

Commit, push, and release.

Deploy and execute drush cim. That should uninstall the module.

A hacky way to uninstall is directly editing the core.extension.yml, remove the complete entry of the module from under the module: key, and executing drush cim

Second release:

Removing module from composer.

answered 32 mins ago

AjitS

10k73266

Yeah, but there may be other config related to that module. If I remember it right, it's not safe to just edit core.extension.yml. The uninstallation routine needs to be triggered, to remove all other related config as well. And that needs to happen before drush cim via an update hook.
â€“Â leymannx
4 mins ago

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "220"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

Francesco is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdrupal.stackexchange.com%2fquestions%2f271202%2fdisabling-module-with-config-sync-and-removing-with-composer%23new-answer', 'question_page');

);

Post as a guest

Name

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
2
down vote

accepted

You need two consecutive releases for stuff like that.

First release:

/**
 * Uninstall SOME_MODULE module.
 */
function MYMODULE_update_8001(&$sandbox) 

 Drupal::service('module_installer')->uninstall(['SOME_MODULE']);

Second release:

The module can be removed via Composer.

Order of drush commands for automated deployment?

edited 32 mins ago

answered 1 hour ago

leymannx

5,89042356

Thanks, everything's clear to me! Thanks also for the related question, very intresting!
â€“Â Francesco
1 hour ago

You actually do not require an update hook just to uninstall the module. The configuration management in D8 could be used for it. Added an alternative answer built on top of your. cc @Francesco
â€“Â AjitS
30 mins ago

@AjitS Ã¢Â€Â“ Unsure about that. When drush cim recognizes some missing config, not knowing that some module will be uninstalled from core.extensions.yml later. If I remember it right this can raise an exception.
â€“Â leymannx
11 mins ago

add a commentÂ |Â

up vote
2
down vote

accepted

You need two consecutive releases for stuff like that.

First release:

/**
 * Uninstall SOME_MODULE module.
 */
function MYMODULE_update_8001(&$sandbox) 

 Drupal::service('module_installer')->uninstall(['SOME_MODULE']);

Second release:

The module can be removed via Composer.

Order of drush commands for automated deployment?

edited 32 mins ago

answered 1 hour ago

leymannx

5,89042356

Thanks, everything's clear to me! Thanks also for the related question, very intresting!
â€“Â Francesco
1 hour ago

You actually do not require an update hook just to uninstall the module. The configuration management in D8 could be used for it. Added an alternative answer built on top of your. cc @Francesco
â€“Â AjitS
30 mins ago

@AjitS Ã¢Â€Â“ Unsure about that. When drush cim recognizes some missing config, not knowing that some module will be uninstalled from core.extensions.yml later. If I remember it right this can raise an exception.
â€“Â leymannx
11 mins ago

add a commentÂ |Â

up vote
2
down vote

accepted

You need two consecutive releases for stuff like that.

First release:

/**
 * Uninstall SOME_MODULE module.
 */
function MYMODULE_update_8001(&$sandbox) 

 Drupal::service('module_installer')->uninstall(['SOME_MODULE']);

Second release:

The module can be removed via Composer.

Order of drush commands for automated deployment?

edited 32 mins ago

answered 1 hour ago

leymannx

5,89042356

You need two consecutive releases for stuff like that.

First release:

/**
 * Uninstall SOME_MODULE module.
 */
function MYMODULE_update_8001(&$sandbox) 

 Drupal::service('module_installer')->uninstall(['SOME_MODULE']);

Second release:

The module can be removed via Composer.

Order of drush commands for automated deployment?

edited 32 mins ago

answered 1 hour ago

leymannx

5,89042356

edited 32 mins ago

answered 1 hour ago

leymannx

5,89042356

answered 1 hour ago

leymannx

5,89042356

answered 1 hour ago

leymannx

5,89042356

Thanks, everything's clear to me! Thanks also for the related question, very intresting!
â€“Â Francesco
1 hour ago

You actually do not require an update hook just to uninstall the module. The configuration management in D8 could be used for it. Added an alternative answer built on top of your. cc @Francesco
â€“Â AjitS
30 mins ago

@AjitS Ã¢Â€Â“ Unsure about that. When drush cim recognizes some missing config, not knowing that some module will be uninstalled from core.extensions.yml later. If I remember it right this can raise an exception.
â€“Â leymannx
11 mins ago

add a commentÂ |Â

Thanks, everything's clear to me! Thanks also for the related question, very intresting!
â€“Â Francesco
1 hour ago

You actually do not require an update hook just to uninstall the module. The configuration management in D8 could be used for it. Added an alternative answer built on top of your. cc @Francesco
â€“Â AjitS
30 mins ago

@AjitS Ã¢Â€Â“ Unsure about that. When drush cim recognizes some missing config, not knowing that some module will be uninstalled from core.extensions.yml later. If I remember it right this can raise an exception.
â€“Â leymannx
11 mins ago

Thanks, everything's clear to me! Thanks also for the related question, very intresting!
â€“Â Francesco
1 hour ago

You actually do not require an update hook just to uninstall the module. The configuration management in D8 could be used for it. Added an alternative answer built on top of your. cc @Francesco
â€“Â AjitS
30 mins ago

@AjitS Ã¢Â€Â“ Unsure about that. When drush cim recognizes some missing config, not knowing that some module will be uninstalled from core.extensions.yml later. If I remember it right this can raise an exception.
â€“Â leymannx
11 mins ago

add a commentÂ |Â

up vote
0
down vote

Adding an alternative solution to @leymannx - you will still need two releases. This is taking into consideration your mention of drush cim

First release:

Uninstall the module drush pmu module_name

Export the configuration.

Commit, push, and release.

Deploy and execute drush cim. That should uninstall the module.

A hacky way to uninstall is directly editing the core.extension.yml, remove the complete entry of the module from under the module: key, and executing drush cim

Second release:

Removing module from composer.

answered 32 mins ago

AjitS

10k73266

Yeah, but there may be other config related to that module. If I remember it right, it's not safe to just edit core.extension.yml. The uninstallation routine needs to be triggered, to remove all other related config as well. And that needs to happen before drush cim via an update hook.
â€“Â leymannx
4 mins ago

add a commentÂ |Â

up vote
0
down vote

Adding an alternative solution to @leymannx - you will still need two releases. This is taking into consideration your mention of drush cim

First release:

Uninstall the module drush pmu module_name

Export the configuration.

Commit, push, and release.

Deploy and execute drush cim. That should uninstall the module.

A hacky way to uninstall is directly editing the core.extension.yml, remove the complete entry of the module from under the module: key, and executing drush cim

Second release:

Removing module from composer.

answered 32 mins ago

AjitS

10k73266

Yeah, but there may be other config related to that module. If I remember it right, it's not safe to just edit core.extension.yml. The uninstallation routine needs to be triggered, to remove all other related config as well. And that needs to happen before drush cim via an update hook.
â€“Â leymannx
4 mins ago

add a commentÂ |Â

up vote
0
down vote

Adding an alternative solution to @leymannx - you will still need two releases. This is taking into consideration your mention of drush cim

First release:

Uninstall the module drush pmu module_name

Export the configuration.

Commit, push, and release.

Deploy and execute drush cim. That should uninstall the module.

A hacky way to uninstall is directly editing the core.extension.yml, remove the complete entry of the module from under the module: key, and executing drush cim

Second release:

Removing module from composer.

answered 32 mins ago

AjitS

10k73266

Adding an alternative solution to @leymannx - you will still need two releases. This is taking into consideration your mention of drush cim

First release:

Uninstall the module drush pmu module_name

Export the configuration.

Commit, push, and release.

Deploy and execute drush cim. That should uninstall the module.

A hacky way to uninstall is directly editing the core.extension.yml, remove the complete entry of the module from under the module: key, and executing drush cim

Second release:

Removing module from composer.

answered 32 mins ago

AjitS

10k73266

answered 32 mins ago

AjitS

10k73266

answered 32 mins ago

AjitS

10k73266

answered 32 mins ago

AjitS

10k73266

Yeah, but there may be other config related to that module. If I remember it right, it's not safe to just edit core.extension.yml. The uninstallation routine needs to be triggered, to remove all other related config as well. And that needs to happen before drush cim via an update hook.
â€“Â leymannx
4 mins ago

add a commentÂ |Â

Yeah, but there may be other config related to that module. If I remember it right, it's not safe to just edit core.extension.yml. The uninstallation routine needs to be triggered, to remove all other related config as well. And that needs to happen before drush cim via an update hook.
â€“Â leymannx
4 mins ago

Yeah, but there may be other config related to that module. If I remember it right, it's not safe to just edit core.extension.yml. The uninstallation routine needs to be triggered, to remove all other related config as well. And that needs to happen before drush cim via an update hook.
â€“Â leymannx
4 mins ago

add a commentÂ |Â

Francesco is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Francesco is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky