> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/2023-2/configuration-manager/golden-configurations/cli-ordered-lists/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# CLI ordering in Golden Configuration

> Enforce configuration line ordering for access control lists

Golden Configuration enables you to check for the existence of a line and then determine whether the existence of that line (or lack thereof) is a compliance failure. However, Golden Config strictly checks whether a line is present or not—it has no concept of whether the line is in the correct order. In scenarios with ACLs (access control lists), native existence checks may not be sufficient since the order of the configuration elements (IP Addresses) is paramount.

This is where CLI Ordering extends the functionality of Golden Config. It allows you to define a configuration scope where ordering of the elements needs to be accounted for. In this guide, you will learn how to enable order checking and how to exclude certain elements from order checking.

## Ordering types

First it is important to know the difference between the two supported types of ordering: strict ordering and loose ordering.

### Strict ordering

Strict ordering declares that the order of the configuration elements must be exactly as defined and it must also be consecutive. Meaning that every element starting from the first element must match the defined order along with every consecutive element in the configuration.

For example, observe this Golden Configuration snippet where a configuration scope is defined to have strict ordering, denoted by the `{lso/}` (list strictly ordered) tag:

```
{lso/}ip access-list extended 101
 permit tcp any host 192.168.2.15
 permit udp any host 10.20.30.40
 deny ip any host 172.16.5.100
 permit ip any any
```

This configuration expects the device to contain an `ip access-list extended 101` in which the first element to the fourth element must be exactly as stated in the declaration. Any element that does not match the desired index will generate a compliance failure indicating that array ordering rules were not met for the specific elements that were out of order.

### Loose ordering

Similarly, loose ordering is defined using the tag `{llo/}` (list loosely ordered). Loose ordering checks that the order you define in Golden Config is met but as long as each consecutive configuration element exists anywhere after the current element, then the ordering is satisfied.

Take the same configuration as strict ordering from above but assign it the loose ordering tag:

```
{llo/}ip access-list extended 101
 permit tcp any host 192.168.2.15
 permit udp any host 10.20.30.40
 deny ip any host 172.16.5.100
 permit ip any any
```

This loose ordering would indicate that:

* `permit tcp any host 10.20.30.40` must exist somewhere after `permit udp any host 192.168.2.15`
* `deny ip any host 172.16.5.100` must exist somewhere after `permit tcp any host 10.20.30.40`
* `permit ip any any` must exist somewhere after `deny ip any host 172.16.5.100`

Loose ordering does not require these elements to be consecutive. Meaning that as long as the order is satisfied from one line to the next, the existence of elements between them will not generate a compliance failure.

With that stated, the following configuration would pass the loose ordering test based on the declaration above:

```
{llo/}ip access-list extended 101
 permit tcp any host 192.168.2.15 <- first expected config line
 permit tcp any host 192.168.3.25
 permit udp any host 10.30.40.50
 permit udp any host 10.20.30.40 <- second expected config line
 deny ip any host 172.17.8.90
 deny ip any host 172.16.5.100 <- third expected config line
 permit tcp any host 192.168.4.60
 permit udp any host 10.40.50.70
 deny ip any host 172.18.9.120
 permit ip any any <- fourth expected config line
```

## Exclude item from list ordering

You may run into a scenario where you want to check the ordering of items within a scope but you also want to check the existence of other items where ordering is not important.

In the ACL example, if you want to check the ordering of elements in the ACL but also want to add a `remark` to add a description to the ACL, then the remark is not relevant to the ordering of the configuration. You can exclude items in an ordered configuration scope by using the tag `{lx/}` (list exclude).

Take the following example of an ACL declaration where a remark is added and excluded from order checking:

```
{lso/}ip access-list extended 101
 {lx/}remark this is my example ACL
 permit tcp any host 192.168.2.15
 permit udp any host 10.20.30.40
 deny ip any host 172.16.5.100
 permit ip any any
```

Since the remark is excluded, it will get checked for existence, whereas the remaining configuration will also get checked for ordering.

## Assign ordering rules

Ordering rules can be assigned from the toolbar menu in the **Configuration** tab of a Golden Configuration:

#### Select parent configuration line

Select the parent configuration line whose child elements you want to check the ordering of.

![](/_fern-img/437ea61376e38bbcadccb4a61995f1b68433cf3e69cd78238f3b482678e731cb.webp)

#### Select ordering type

Hover over the **List Operations** menu in the toolbar (denoted by three stacked horizontal lines) and select the ordering you want to assign—`strict` or `loose`.

![](/_fern-img/67682f1ccde8ad6fd268d9bd07b29f8edc9afa94887b55f0db8178b37e7f256a.webp)

#### Verify tag

Verify the appropriate tag was added to the configuration line.

![](/_fern-img/a3a1393d3d7f60fca04dd95c61a250082d2243e8c9acbfa3b389248f86e8695f.webp)

## Assign ordering exclusion rule

To exempt a configuration line from order checking, you can add the exclusion rule through the same menu:

#### Select child configuration line

Select the child configuration line you want to exempt from order checking.

![](/_fern-img/d7106775f4729430c7001d797e58ccfcac4271ad9b030fa97cb87d772ca8efe0.webp)

#### Select exclusion option

Hover over the **List Operations** menu in the toolbar and select `Exclude item from list ordering`.

![](/_fern-img/ea0229389b192224a0e06a7a52db6edca2380433018710f939532d4ef5205c96.webp)

#### Verify exclusion tag

Verify the appropriate tag `{lx/}` was added to the configuration line.

![](/_fern-img/139a27475771749099d5a5a6971e0b208f1b04e8d215963d8579ec303866575b.webp)

## CLI exclusivity

You may run into a scenario where you want to check the existence of the elements you defined but also want to automatically disallow anything else that you did not specifically define. This concept can be referred to as Ghost Configuration. Golden Configuration now enables you to check for Ghost Configurations using the `{only/}` tag.

Ghost Configuration checking rules can only be assigned to a parent configuration line; therefore only child elements can be identified as ghost elements.

In the following example, the `{only/}` tag is assigned to the parent ACL element to check for Ghost Configuration. This will ensure the three IP addresses you have defined in your configuration exist and any other configurations found in the scope of that ACL will automatically get tagged for removal in a compliance report.

```
{only/}ip access-list extended Standard-ACL
  permit ip 10.0.1.0 0.0.0.255 any
  permit ip 10.0.2.0 0.0.0.255 any
  permit ip 10.0.3.0 0.0.0.255 any
```

### Assign CLI exclusivity

Exclusivity can be assigned from the toolbar menu in the **Configuration** tab of a Golden Configuration:

#### Select parent configuration line

Select the parent configuration line whose child elements you want to check the ghost configuration of.

![](/_fern-img/64cc91cf21356b17a85622f6b7123305127e7c8d185c47cde270401c52d0458b.webp)

#### Select exclusivity option

Hover over the **List Operations** menu in the toolbar and select `Only allow these items`.

![](/_fern-img/83102476f6cb55b4ef3f53389e21f2a79c3958cce0e7e3b1648664cc0874f69a.webp)

#### Verify exclusivity tag

Verify the appropriate tag `{only/}` was added to the parent configuration line.

![](/_fern-img/c6837898a5bbf184adaf09195f83557c1378777c18f08c100fbaa0df07751981.webp)

> Enforce configuration line ordering for access control lists