Problem/Motivation

Minimum ACs

  • "Batch Op Log" entity that will track the following
    • What script ran (string) - the main identifier
    • What ran it (drush, UI, hook_updateN, post update, deploy hook, post deploy)
    • Who ran it (user entity reference)
    • when it started (timestamp)
    • when the last operation ocurred (timestamp)
    • Whether the operation was completed (boolean)
    • Log (long text) - Concat text (appended to by each processOne()} (as though watching in the terminal)
    • any caught errors or exceptions (long text)
  • Needs a separate "View batch operations log" permission
  • Documented in the README

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

swirt created an issue. See original summary.

swirt’s picture

Version: » 1.0.x-dev
Issue summary: View changes
swirt’s picture

Issue summary: View changes
swirt’s picture

Issue summary: View changes
swirt’s picture

Issue summary: View changes

swirt’s picture

Issue summary: View changes
swirt’s picture

This is driving me a bit nuts. I am sure something obvious is staring me in the face, but I don't see it yet.

The route exists. It is revealed with drush route --path=/admin/config/development/batch_operations/log/1
But going to the location after creating the first log entity returns page not found. Same for the collection page.

swirt’s picture

It now has the ability to #3425751: Add list View to see all script logs and delete them... but still can't view them

  • swirt committed 79b74c45 on 1.0.x
    #3425026 Add BatchOpLog entity.
    
swirt’s picture

Status: Active » Fixed

This has been merged.

swirt’s picture

Status: Fixed » Closed (fixed)