This directory contains an idiomatic C++ client library for the Certificate Authority API. The Certificate Authority Service API is a highly-available, scalable service that enables you to simplify and automate the management of private certificate authorities (CAs) while staying in control of your private keys.

While this library is GA, please note that the Google Cloud C++ client libraries do not follow Semantic Versioning.

• Windows, macOS, Linux
• C++14 (and higher) compilers (we test with GCC >= 7.3, Clang >= 6.0, and MSVC >= 2017)
• Environments with or without exceptions
• Bazel (>= 4.0) and CMake (>= 3.5) builds

• Official documentation about the Certificate Authority API service
• Reference doxygen documentation for each release of this client library
• Detailed header comments in our public .h files

The quickstart/ directory contains a minimal environment to get started using this client library in a larger project. The following "Hello World" program is used in this quickstart, and should give you a taste of this library.

#include "google/cloud/privateca/certificate_authority_client.h"
#include <iostream>

int main(int argc, char* argv[]) try {
  if (argc != 3) {
    std::cerr << "Usage: " << argv[0] << " project-id location-id\n";
    return 1;
  }

  namespace privateca = ::google::cloud::privateca;
  auto client = privateca::CertificateAuthorityServiceClient(
      privateca::MakeCertificateAuthorityServiceConnection());

  auto const ca_pool =
      "projects/" + std::string(argv[1]) + "/locations/" + std::string(argv[2]);
  for (auto r : client.ListCaPools(ca_pool)) {
    if (!r) throw std::move(r).status();
    std::cout << r->DebugString() << "\n";
  }

  return 0;
} catch (google::cloud::Status const& status) {
  std::cerr << "google::cloud::Status thrown: " << status << "\n";
  return 1;
}

• Packaging maintainers or developers who prefer to install the library in a fixed directory (such as /usr/local or /opt) should consult the packaging guide.
• Developers that prefer using a package manager such as vcpkg, Conda, or Conan should follow the instructions for their package manager.
• Developers wanting to use the libraries as part of a larger CMake or Bazel project should consult the quickstart guides for the library or libraries they want to use.
• Developers wanting to compile the library just to run some examples or tests should read the current document.
• Contributors and developers to google-cloud-cpp should consult the guide to setup a development workstation.

See CONTRIBUTING.md for details on how to contribute to this project, including how to build and test your changes as well as how to properly format your code.

Apache 2.0; see LICENSE for details.