inspec/docs/resources/bridge.md.erb

48 lines
1.3 KiB
Text
Raw Normal View History

2016-09-22 12:43:57 +00:00
---
title: About the bridge Resource
---
# bridge
Use the `bridge` InSpec audit resource to test basic network bridge properties, such as name, if an interface is defined, and the associations for any defined interface.
* On Linux platforms, any value in the `/sys/class/net/{interface}/bridge` directory may be tested
* On the Windows platform, the `Get-NetAdapter` cmdlet is associated with the `Get-NetAdapterBinding` cmdlet and returns the `ComponentID ms_bridge` value as a JSON object
<br>
## Syntax
2016-09-22 12:43:57 +00:00
A `bridge` resource block declares the bridge to be tested and what interface it should be associated with:
describe bridge('br0') do
it { should exist }
it { should have_interface 'eth0' }
end
<br>
2016-09-22 12:43:57 +00:00
## Matchers
2016-09-22 12:43:57 +00:00
For a full list of available matchers please visit our [matchers page](https://www.inspec.io/docs/reference/matchers/).
2016-09-22 12:43:57 +00:00
### exist
2016-09-22 12:43:57 +00:00
The `exist` matcher tests if the network bridge is available:
it { should exist }
### have_interface
2016-09-22 12:43:57 +00:00
The `have_interface` matcher tests if the named interface is defined for the network bridge:
it { should have_interface 'eth0' }
### interfaces
2016-09-22 12:43:57 +00:00
The `interfaces` matcher tests if the named interface is present:
its('interfaces') { should eq 'foo' }
its('interfaces') { should eq 'bar' }
its('interfaces') { should include('foo') }