Method remove

src/resource_provider/daemon.cpp:312–358

Future<Nothing> LocalResourceProviderDaemonProcess::remove(
    const string& type,
    const string& name)
{
  if (configDir.isNone()) {
    return Failure("Missing required flag --resource_provider_config_dir");
  }

  // Do nothing if the info has been removed for idempotency.
  if (!providers[type].contains(name)) {
    return Nothing();
  }

  ProviderData& data = providers[type].at(name);

  // Return the same future if it is being removed for idempotency.
  if (data.removing.isSome() && data.removing->isPending()) {
    return data.removing.get();
  }

  // Destruct the resource provider instance to stop its container daemons, then
  // do a best-effort cleanup of the standalone containers launched by the
  // removed resource provider.
  // TODO(chhsiao): This is not ideal since the daemon does not know how to
  // perform resource-provider-specific cleanups. We should refactor this into a
  // `LocalResourceProvider::stop` virtual function. However this also means
  // that we need to ensure that we must have a resource provider instance with
  // a running actor to invoke `stop`. Given that `launch` is asynchronous, we
  // need to carefully redesign the state machine, and the semantics of the
  // `{ADD,UPDATE,REMOVE}_RESOURCE_PROVIDER_CONFIG` API calls might be affected.
  // In addition, we should consider how to reconcile orphaned containers.
  data.provider.reset();
  data.removing = cleanupContainers(data.info, data.authToken)
    .then(defer(self(), [this, type, name]() -> Future<Nothing> {
      Try<Nothing> rm = os::rm(providers[type].at(name).path);
      if (rm.isError()) {
        return Failure(
            "Failed to remove config file '" + providers[type].at(name).path +
            "': " + rm.error());
      }

      providers[type].erase(name);
      return Nothing();
    }));

  return data.removing.get();
}


void LocalResourceProviderDaemonProcess::initialize()