Skip to content

feat: add confirmation prompts for deleting runtime journals and synchronous user confirmation function#4632

Merged
jlhughes merged 1 commit intodevelopmentfrom
confirmation-message-on--j
Nov 25, 2025
Merged

feat: add confirmation prompts for deleting runtime journals and synchronous user confirmation function#4632
jlhughes merged 1 commit intodevelopmentfrom
confirmation-message-on--j

Conversation

@abdelaziz-mahdy
Copy link
Collaborator

to avoid mistakenly deleting the journals on building with -j

@jlhughes
Copy link
Collaborator

No, use -N
./build.sh help:N
this deploys to a uniquely named deployment directory. You can have as many as you want.
It can be used for running multiple JVMs locally, and in this case you need the -W option so each gets a unique set of ports.
Works just as well for quickly running against staging or production data.
copy staging data to /opt/staging (for example), and then run with -Nstaging
Keep as many journal sets around as you like.

@jlhughes jlhughes merged commit ccfdb30 into development Nov 25, 2025
1 check passed
}
}

function confirmSync(message) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this 'Sync' if it returns a Promise?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#4634 removes it, since its not used anymore.

}],

deleteRuntimeJournals: ['delete-runtime-journals', 'Delete runtime journals.', [], function() {
// Confirmation check to protect against accidental journal deletion
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't it be better to leave this task alone and either create a new one called 'safely-delete-runtime-journals' which ask for the confirmation or one called 'delete-runtime-journals-with-backup' which just moves the journals to something like journals.backup. instead. If anyone is scripting the build there would be nobody around to confirm.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

f6ec96e Joel added auto confirm. so its like force for scripting approaches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants