-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #137 from lpeidro/feature/protected-instances-drus…
…h-commands Added Drush PolicyCommands
- Loading branch information
Showing
3 changed files
with
61 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
Drush command policies have been implemented to prevent the execution of certain drush commands: 'core:sync', | ||
'sql:sync', and 'sql:drop' in production or other environment instances. | ||
|
||
To apply these policies, two actions must be taken: | ||
- In the definition of the alias for the environment where you want these policies to be applied you have to add the parameter: "protected-instance: true" | ||
- On the server of the environment, copy the 'drush/Commands/drush.yml.dist' to the user's .drush folder of the user used for SSH connections to the server. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# This configuration file must be copied to the user's .drush folder in the environment where we want to enable | ||
# protection for commands that may drop or overwrite the database. | ||
protected-instance: true |