-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE: cr:list
command
#4900
base: 9.0
Are you sure you want to change the base?
FEATURE: cr:list
command
#4900
Conversation
26fff3a
to
4cb1889
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slightly more changes than indicated in the title. 🤨
@@ -33,6 +33,11 @@ class ContentStreamCommandController extends CommandController | |||
*/ | |||
public function pruneCommand(string $contentRepository = 'default', bool $removeTemporary = false): void | |||
{ | |||
if (!$this->output->askConfirmation(sprintf('> This operation in "%s" cannot be reverted. Are you sure to proceed? (y/n) ', $contentRepository), false)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mhsdesign What was the intention on adding this unskippable confirmation? I remember using the pruneCommand
and pruneRemovedFromEventStreamCommand
regularly to cleanup the database.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its a safety measurement we already have in place in other locations but forgot about this one ... like cr:prune
and cr:projectionReplay
etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm. But do we really assume that this commands will only ever have the need to be triggered manually? Cleaning up the contentstream tables of junk data is a bit of a different use case then cr:prune
and cr:projectionReplay
.
And I'm worried about adding this change now in a feature PR without addressing it. This might be a change someone running an active Neos 9 project would like to see in the Logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Imho this must be able to be part of a deployment process, so at least a confirmation parameter must be added to the CLI call.
future idea from christian: show also if there is a mismatch between actual dimensions and configured ones ... that will make this clearly a |
advanced / verbose output (using internal stuff)
Upgrade instructions
Review instructions
Checklist
FEATURE|TASK|BUGFIX
!!!
and have upgrade-instructions