Renamed the set_level message field in SetLogLevelRequest to new_level.

The name new_level better expresses the intent of the field, set_level is not quite as expressive. Signed-off-by: Edwin Buck <[email protected]>
spiffe · Feb 22, 2024 · 7dd67c1 · 7dd67c1
1 parent e2d4e78
commit 7dd67c1
Show file tree

Hide file tree

Showing 4 changed files with 15 additions and 15 deletions.
diff --git a/proto/spire/api/agent/logger/v1/logger.pb.go b/proto/spire/api/agent/logger/v1/logger.pb.go
diff --git a/proto/spire/api/agent/logger/v1/logger.proto b/proto/spire/api/agent/logger/v1/logger.proto
@@ -31,7 +31,7 @@ message GetLoggerRequest {
 message SetLogLevelRequest {
 
     // The new level the logger should assume
-    spire.api.types.LogLevel set_level = 1;
+    spire.api.types.LogLevel new_level = 1;
 }
 
 // Empty Reset Log Level Request message for future extension

diff --git a/proto/spire/api/server/logger/v1/logger.pb.go b/proto/spire/api/server/logger/v1/logger.pb.go
diff --git a/proto/spire/api/server/logger/v1/logger.proto b/proto/spire/api/server/logger/v1/logger.proto
@@ -31,7 +31,7 @@ message GetLoggerRequest {
 message SetLogLevelRequest {
 
     // The new level the logger should assume
-    spire.api.types.LogLevel set_level = 1;
+    spire.api.types.LogLevel new_level = 1;
 
 }