Title: raywalker's Replies | WordPress.org

---

# raywalker

  [  ](https://wordpress.org/support/users/raywalker/)

 *   [Profile](https://wordpress.org/support/users/raywalker/)
 *   [Topics Started](https://wordpress.org/support/users/raywalker/topics/)
 *   [Replies Created](https://wordpress.org/support/users/raywalker/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/raywalker/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/raywalker/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/raywalker/engagements/)
 *   [Favorites](https://wordpress.org/support/users/raywalker/favorites/)

 Search replies:

## Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] WAF rules in a stateless environment](https://wordpress.org/support/topic/waf-rules-in-a-stateless-environment/)
 *  Thread Starter [raywalker](https://wordpress.org/support/users/raywalker/)
 * (@raywalker)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/waf-rules-in-a-stateless-environment/#post-11559643)
 * Okay thanks for the update Dave. We’ve applied the workaround on container start
   and it does the job for now.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] WAF rules in a stateless environment](https://wordpress.org/support/topic/waf-rules-in-a-stateless-environment/)
 *  Thread Starter [raywalker](https://wordpress.org/support/users/raywalker/)
 * (@raywalker)
 * [7 years, 3 months ago](https://wordpress.org/support/topic/waf-rules-in-a-stateless-environment/#post-11549432)
 * Thanks Gerroald,
 * This solution appears to work for a single pod. Unfortunately this seems to work
   only for the pod in which the command is executed and doesn’t affect all pods
   sharing a common DB. It also must be reapplied whenever pods are rescheduled,
   restarted, or the deployment scaled out. We’re running multiple pods for HA /
   performance and autoscaling according to load.
 * We can workaround by applying this on container start, but is there any way to
   store this configuration option that will persist in the above scenarios?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP-Stateless - Google Cloud Storage] Switch bucket functionality](https://wordpress.org/support/topic/switch-bucket-functionality/)
 *  [raywalker](https://wordpress.org/support/users/raywalker/)
 * (@raywalker)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/switch-bucket-functionality/#post-10715356)
 * Further to the above, it seems it’s possible to fix buckets after a move by running
   the Sync command from WP Stateless settings.
 * Is there any way of calling this function in an automation environment – API,
   wp-cli etc?

Viewing 3 replies - 1 through 3 (of 3 total)