Skip to content

[sec_scan][2] expose ssh_scan_enabled in AccessGraphConfig response #43467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tigrato merged 1 commit into from
Jul 9, 2024
Merged

[sec_scan][2] expose ssh_scan_enabled in AccessGraphConfig response #43467

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
130 changes: 107 additions & 23 deletions api/gen/proto/go/teleport/clusterconfig/v1/access_graph.pb.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 8 additions & 0 deletions api/proto/teleport/clusterconfig/v1/access_graph.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,4 +30,12 @@ message AccessGraphConfig {
// insecure is a flag that indicates whether the access graph service should
// skip verifying the server's certificate chain and host name.
bool insecure = 4;
// secrets_scan_config is used to configure the parameters for the secrets scanning functionality.
AccessGraphSecretsScanConfiguration secrets_scan_config = 5;
}

// AccessGraphSecretsScanConfiguration controls the secrets scanning service parameters.
message AccessGraphSecretsScanConfiguration {
// ssh_scan_enabled indicates if the SSH scan feature is enabled for the cluster.
bool ssh_scan_enabled = 1;
}