<?php
/**
 * POST cortex/v1/sync/run.
 *
 * @package CortexCommerce
 */

namespace CortexCommerce\Rest;

use CortexCommerce\Settings\Options;
use CortexCommerce\Sync\ProductSyncSender;

defined( 'ABSPATH' ) || exit;

/**
 * The product sync's next run, started by the plugin itself (ProductSync::chain()) in a new PHP process. There is no
 * user check: the run that chains it may have been started by WP-Cron with nobody logged in, so the request carries
 * no cookie or key, and the sender reads the catalog as nobody anyway. The X-Cortex-Run-Token header is the only
 * credential: a single-use token the chaining run stored, accepted once and for two minutes. A request without it is
 * refused, even from a logged-in administrator.
 */
final class SyncRunController {

	public function register_routes(): void {
		register_rest_route(
			RestModule::NAMESPACE,
			'/sync/run',
			array(
				array(
					'methods'             => 'POST',
					'callback'            => array( $this, 'post' ),
					'permission_callback' => array( self::class, 'permission' ),
				),
			)
		);
	}

	/**
	 * WordPress calls a permission callback a second time, from rest_send_allow_header() in serve_request(). That
	 * second call fails harmlessly because the token is already consumed, so this method must never log or count a
	 * failed attempt.
	 *
	 * @return true|\WP_Error
	 */
	public static function permission( \WP_REST_Request $request ) {
		if ( Options::consume_run_token( (string) $request->get_header( 'x-cortex-run-token' ) ) ) {
			return true;
		}
		return new \WP_Error(
			'cortexcommerce_rest_forbidden',
			__( 'Sorry, you are not allowed to do that.', 'cortexcommerce' ),
			array( 'status' => 403 )
		);
	}

	public function post(): \WP_REST_Response {
		// The caller hangs up at once, as wp-cron's spawn does: keep running so the push is not cut off mid-run.
		ignore_user_abort( true );
		ProductSyncSender::run();
		return new \WP_REST_Response( null, 202 );
	}
}