Provide an action plugin

Hi @jurgenhaas,
I just read your feature request and it sounds like a really cool request. If you're already working on that and wanna open a MR please do. I'll be happy to try it out and add it to the module.

Thanks again,
aronne

I'm more of an end user and I'll be happy to help in use cases.

Also very helpful if the client manager can catch error codes and make them accessible as tokens for later use elsewhere (say, in ECA, VBO etc.), such that end users can perform necessary actions after catching error the codes.

Hi @jurgenhaas and @amal.bukhari

Services API list

you can use the http_client_manager.http_services_api service to get a list of all the available services API.
eg: \Drupal::service('http_client_manager.http_services_api')->getServicesApi()

You can find an example usage here: https://git.drupalcode.org/project/http_client_manager/-/blob/9.3.x/src/...

Services API Commands list

Also, you can get a list of all the Service API Commands in that way:

$client = \Drupal::service('http_client_manager.factory')->get($serviceApi);
$commands = $client->getCommands();

Another example usage: https://git.drupalcode.org/project/http_client_manager/-/blob/9.3.x/src/...

Error handling

You can either use a try catch:

try {
  return $httpClient->call($command, $args);
}
catch (CommandException $e) {
  // do something here.
}

or use an HTTP Service API Wrapper as explained here https://www.drupal.org/docs/contributed-modules/http-client-manager/http... and override the basic implementation of the logError method:

/**
   * Logs a command exception.
   *
   * This method is meant to be overridden by any Service Api Wrapper.
   * By default it prints the error message by using the Messenger service.
   *
   * @param \GuzzleHttp\Command\Exception\CommandException $e
   *   The Command Exception object.
   */
  protected function logError(CommandException $e) {
    $this->messenger->addError($e->getMessage());
  }

Preconfigured requests

You can create them for every command defined in you http services api. https://www.drupal.org/docs/8/modules/http-client-manager/http-config-re...
You can list them all by using the entity_type.manager service, since they are ConfigEntities.

\Drupal::entityTypeManager()->getStorage('http_config_request')->loadByProperties()

Hope it helps!

I took a look at your implementation and I really like it. About the storing of results I agree with you on using the expirable key_value storage or even the StateApi.
You could try and go ahead with the expirable key_value and see how it goes.

Yes I know @jurgenhaas
for now don't care about that bug. I'm gonna work on it in a separate issue tomorrow.

Hi @jurgenhaas
I'm working on this issue #3323767: Add a data integrity layer which should fix the problem you raised.

It should be available soon.

Hi @jurgenhaas,
could you try and apply the patch I provided on the following issue? #3323767: Add a data integrity layer
Let me know if it works for you together with your implementation.

Available @dev version

Yes of course! done ;)