Skip to content

Build wp altis post-sync CLI command #1298

@VlasicVojislav

Description

@VlasicVojislav

Description

We need to build a wp altis post-sync CLI command where projects can run our default actions and their own actions as well.
List of our actions:

  • Flush object cache
  • Reindex elasticsearch if available
  • Truncate cavalcade logs in the DB

Potential customer actions:

  • Anonymize data
  • Truncate tables / data so the data set is smaller
  • Update options

Acceptance criteria

  • WP CLI command calls the action
  • Flush object cache is hooked to the action
  • Reindex elasticsearch is hooked to the action
  • Truncate cavalcade logs in the DB is hooked to the action
  • Our actions can be unhooked (they shouldn't be anonymous actions)
  • Document what our code does - everything works through altis post-sync CLI command and not directly to redis for example.
  • Document some useful customer examples (turn off analytics, turn off automatic API calls, etc.)

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to a milestone?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
  • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
  • Is there a roll-out (and roll-back) plan if required?

Metadata

Metadata

Assignees

No one assigned

    Labels

    must haveMust be done, high priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions