Skip to content

Commit 217bb87

Browse files
authored
Merge pull request #381 from miharp/docs/retire-ldap-node-classifier-278
Retire LDAP node classifier docs (the ldap node terminus was removed in OpenVox 8)
2 parents 9c786f0 + 0fc2b59 commit 217bb87

4 files changed

Lines changed: 1 addition & 231 deletions

File tree

_data/nav/openvox_8x.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -341,8 +341,6 @@
341341
items:
342342
- text: External node classifiers
343343
link: "nodes_external.html"
344-
- text: The LDAP node classifier
345-
link: "nodes_ldap.html"
346344
- text: Misc. references
347345
items:
348346
- text: Settings (configuration reference)

docs/_openvox_8x/lang_classes.markdown

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@ title: "Language: Classes"
3434
[declare]: #declaring-classes
3535
[setting_parameters]: #include-like-vs-resource-like
3636
[override]: #using-resource-like-declarations
37-
[ldap_nodes]: ./nodes_ldap.html
3837
[hiera]: /openvox/latest/hiera_intro.html
3938
[external_data]: /openvox/latest/hiera_automatic.html
4039
[array_search]: /openvox/latest/hiera_merging.html
@@ -396,7 +395,7 @@ However, note that:
396395

397396
## Assigning classes from an ENC
398397

399-
Classes can also be assigned to nodes by [external node classifiers][enc] and [LDAP node data][ldap_nodes]. Note that most ENCs assign classes with include-like behavior, and some ENCs assign them with resource-like behavior. See the [documentation of the ENC interface][enc] or the documentation of your specific ENC for complete details.
398+
Classes can also be assigned to nodes by [external node classifiers][enc]. Note that most ENCs assign classes with include-like behavior, and some ENCs assign them with resource-like behavior. See the [documentation of the ENC interface][enc] or the documentation of your specific ENC for complete details.
400399

401400
## Appendix: Smart parameter defaults
402401

docs/_openvox_8x/nodes_ldap.md

Lines changed: 0 additions & 224 deletions
This file was deleted.

docs/_openvox_8x/subsystem_catalog_compilation.markdown

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,6 @@ title: "Subsystems: Catalog compilation"
1818
[node terminus]: ./configuration.html#node_terminus
1919
[plain_node]: ./indirection.html#plain-terminus
2020
[exec_node]: ./indirection.html#exec-terminus
21-
[ldap_guide]: ./nodes_ldap.html
2221
[facts_builtin]: ./lang_facts_and_builtin_vars.html
2322
[node definitions]: ./lang_node_definitions.html
2423
[agent_provided]: #agent-provided-data
@@ -108,8 +107,6 @@ By default, OpenVox Server uses the [`plain` node terminus][plain_node], which j
108107

109108
The next most common node terminus is the [`exec` node terminus][exec_node], which will request data from an [external node classifier (ENC)][enc]. This can return classes, variables, an environment, or some combination of the three, depending on how the ENC is designed.
110109

111-
Less commonly, some people use the `ldap` node terminus, which will fetch ENC-like information from an LDAP database. See the page on [LDAP nodes][ldap_guide] for more information.
112-
113110
Finally, it's possible to write a custom node terminus that retrieves classes, variables, and environments from any kind of external system.
114111

115112
### Step 2: Set variables from the node object, from facts, and from the certificate

0 commit comments

Comments
 (0)