Cole-Greer commented on code in PR #3384:
URL: https://github.com/apache/tinkerpop/pull/3384#discussion_r3127666179


##########
docs/src/reference/gremlin-applications.asciidoc:
##########
@@ -1278,14 +1337,20 @@ consult the documentation of the graph you are using to 
determine what authoriza
 
 Gremlin Server supports three mechanisms to configure authorization:
 
-. With the `ScriptFileGremlinPlugin` a groovy script is configured that 
instantiates the `GraphTraversalSources` that
-can be accessed by client requests. Using the `withStrategies()` gremlin
-link:https://tinkerpop.apache.org/docs/x.y.z/reference/#start-steps[start 
step], one can apply so-called
-link:https://tinkerpop.apache.org/docs/x.y.z/reference/#traversalstrategy[TraversalStrategy
 instances] to these
-`GraphTraversalSource` instances, some of which can serve for authorization 
purposes (`ReadOnlyStrategy`,
+. With the `traversalSources` YAML configuration, one can declare 
`TraversalSource` instances with
+link:https://tinkerpop.apache.org/docs/x.y.z/reference/#traversalstrategy[TraversalStrategy
 instances] applied via
+a Gremlin query, some of which can serve for authorization purposes 
(`ReadOnlyStrategy`,
 `LambdaRestrictionStrategy`, `VertexProgramRestrictionStrategy`, 
`SubgraphStrategy`, `PartitionStrategy`,
 `EdgeLabelVerificationStrategy`), provided that users are not allowed to 
remove or modify these `TraversalStrategy`
-instances afterwards. The `ScriptFileGremlinPlugin` is found in the yaml 
configuration file for Gremlin Server:
+instances afterwards. For example:
++
+[source,yaml]
+----
+traversalSources: {
+  g: {graph: graph, query: "g.withStrategies(ReadOnlyStrategy)"}}
+----
++
+Alternatively, the deprecated `ScriptFileGremlinPlugin` approach can still be 
used with a Groovy script:

Review Comment:
   I've changed how the groovy configs are presented in the docs. I don't want 
to completely remove it from the docs as long as it still exists, but I'm now 
framing it as clearly a deprecated legacy option which points to the new config 
as the recommended path.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to