|
|
|
syntax = "proto3";
|
|
|
|
|
|
|
|
package envoy.admin.v2alpha;
|
|
|
|
|
|
|
|
import "google/protobuf/timestamp.proto";
|
|
|
|
|
|
|
|
import "udpa/annotations/status.proto";
|
|
|
|
|
|
|
|
option java_package = "io.envoyproxy.envoy.admin.v2alpha";
|
|
|
|
option java_outer_classname = "CertsProto";
|
|
|
|
option java_multiple_files = true;
|
|
|
|
option (udpa.annotations.file_status).package_version_status = FROZEN;
|
|
|
|
|
|
|
|
// [#protodoc-title: Certificates]
|
|
|
|
|
|
|
|
// Proto representation of certificate details. Admin endpoint uses this wrapper for `/certs` to
|
|
|
|
// display certificate information. See :ref:`/certs <operations_admin_interface_certs>` for more
|
|
|
|
// information.
|
|
|
|
message Certificates {
|
|
|
|
// List of certificates known to an Envoy.
|
|
|
|
repeated Certificate certificates = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
message Certificate {
|
|
|
|
// Details of CA certificate.
|
|
|
|
repeated CertificateDetails ca_cert = 1;
|
|
|
|
|
|
|
|
// Details of Certificate Chain
|
|
|
|
repeated CertificateDetails cert_chain = 2;
|
|
|
|
}
|
|
|
|
|
|
|
|
// [#next-free-field: 7]
|
|
|
|
message CertificateDetails {
|
|
|
|
// Path of the certificate.
|
|
|
|
string path = 1;
|
|
|
|
|
|
|
|
// Certificate Serial Number.
|
|
|
|
string serial_number = 2;
|
|
|
|
|
|
|
|
// List of Subject Alternate names.
|
|
|
|
repeated SubjectAlternateName subject_alt_names = 3;
|
|
|
|
|
|
|
|
// Minimum of days until expiration of certificate and it's chain.
|
|
|
|
uint64 days_until_expiration = 4;
|
|
|
|
|
|
|
|
// Indicates the time from which the certificate is valid.
|
|
|
|
google.protobuf.Timestamp valid_from = 5;
|
|
|
|
|
|
|
|
// Indicates the time at which the certificate expires.
|
|
|
|
google.protobuf.Timestamp expiration_time = 6;
|
|
|
|
}
|
|
|
|
|
|
|
|
message SubjectAlternateName {
|
|
|
|
// Subject Alternate Name.
|
|
|
|
oneof name {
|
|
|
|
string dns = 1;
|
api: protoxform tool and API reformat. (#8309)
This patch introduces a new tool, protoxform, that will be the basis of
the v2 -> v3 migration tooling. It operates as a Python protoc plugin,
within the same framework as protodoc, and provides the ability to
operate on protoc AST input and generate proto output.
As a first step, the tool is applied reflexively on v2, and functions as
a formatting tool. In later patches, this will be added to
check_format/fix_format scripts and CI.
Part of #8082.
Risk level: medium (it's possible that some inadvertent wire changes
occur, if they do, this patch should be rolled back).
Testing: manual inspection of diff, bazel test //test/..., some
grep/diff scripts to ensure we haven't lost any comments.
Signed-off-by: Harvey Tuch <htuch@google.com>
Mirrored from https://github.com/envoyproxy/envoy @ 08b123a8321d359ea66cbbc0e2926545798dabd3
5 years ago
|
|
|
|
|
|
|
string uri = 2;
|
|
|
|
|
|
|
|
string ip_address = 3;
|
|
|
|
}
|
|
|
|
}
|