Deleting unused credentials query language

Author: jglick

docs/consumer.adoc

@@ -281,26 +281,6 @@ We leverage the https://plugins.jenkins.io/authentication-tokens[Authentication
 This means that we can use the `AuthenticationTokens.matcher(Class)` to restrict the list of credentials to the subset that can be converted.
 Alternatively, more complex conversion contexts can be handled with `AuthenticationTokens.matcher(AuthenticationTokenContext)`
 
-* We want to let the user select the credentials to toggle the deployment state of a blue/green deployment for a completed build.
-+
-[source,java]
-----
-CredentialsProvider.listCredentialsInItem(
-    StandardCredentials.class, // <1>
-    job,
-    Jenkins.getAuthentication2(), // <2>
-    URIRequirementBuilder.fromUri(loadBalancerUrl),
-    CredentialsMatchers.allOf(
-      AuthenticationTokens.matcher(LoadBalancerAuthentication.class),
-      CredentialsMatchers.withProperty("permission", "lb.switch") // <3>
-    )
-)
-----
-<1> There are different credential types that can be used to authenticate with the load balancer, this is the common base class.
-<2> This is an immediate action performed by the user.
-<3> In this case there may be multiple credentials available to the user, we only want the ones with `"lb.switch".equals(credential.getPermission())`.
-Any credentials that do not have a `getPermission()` method will be excluded as well as any that do not have the corresponding return value.
-
 * We want to let the user specify the credentials used to update the post commit receive hooks of a source control system for any corresponding jobs configured in Jenkins.
 +
 [NOTE]

docs/implementation.adoc

@@ -576,7 +576,6 @@ The `CredentialsProvider` extension point is perhaps one of the more complicated
 * Where the backing store is remote from Jenkins then:
 
 ** potentially has to be able to either instantiate `java.lang.reflect.Proxy` implementations for credentials, or create on-demand implementation classes using http://asm.ow2.org/[ASM] (or similar).
-** potentially has to deal with parsing the `CredentialsMatcher` query language in order to minimize transfer of information over the network.
 ** may need to store Jenkins specific state in Jenkins in order to provide credentials domain support.
 
 * Where the backing store is local to Jenkins but contextual to a specific Jenkins model object and not covered by the three existing credentials providers: System, User and Folder, then replication of that code will likely be required.
@@ -597,7 +596,6 @@ These existing examples are probably not good as reference examples as they have
 +
 A good reference implementation would be clean of such distractions.
 * [ ] Provide links to some other implementations of credentials providers for other use cases.
-* [ ] Provide some details on how the Credentials Query Language can be used to limit querying credentials from the remote service
 
 ====
 

pom.xml

@@ -186,23 +186,6 @@
           <compatibleSinceVersion>1354</compatibleSinceVersion>
         </configuration>
       </plugin>
-      <plugin>
-        <groupId>org.antlr</groupId>
-        <artifactId>antlr4-maven-plugin</artifactId>
-        <!-- This must be compatible with the ANTLR runtime provided by Jenkins core. -->
-        <version>4.13.2</version>
-        <configuration>
-          <listener>true</listener>
-          <visitor>true</visitor>
-        </configuration>
-        <executions>
-          <execution>
-            <goals>
-              <goal>antlr4</goal>
-            </goals>
-          </execution>
-        </executions>
-      </plugin>
     </plugins>
   </build>
 </project>