Skip to content
This repository has been archived by the owner on May 19, 2020. It is now read-only.

mjmenger/inspec-bigip

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Archived

This repository is no longer maintained. Please use F5 Solutions Engineering's BIG-IP ATC Ready InSpec profile.

BIG-IP Automation Toolchain InSpec Profile

This InSpec profile evaluates the following:

  • basic connectivity to a BIG-IP management endpoint ('bigip-connectivity')
  • availability of the Declarative Onboarding (DO) service ('bigip-declarative-onboarding')
  • version reported by the Declarative Onboarding (DO) service ('bigip-declarative-onboarding-version')
  • availability of the Application Services (AS3) service ('bigip-application-services')
  • version reported by the Application Services (AS3) service ('bigip-application-services-version')
  • availability of the Telemetry Streaming (TS) service ('bigip-telemetry-streaming')
  • version reported by the Telemetry Streaming (TS) service ('bigip-telemetry-streaming-version')
  • availability of a license on the BIG-IP ('bigip-licensed')

In order to reference the profile you can include it as a dependency in your inspec.yml file

depends:
  - name: bigip-atc
    git: https://github.com/mjmenger/inspec-bigip
    branch: master

and indicate which controls to use in your control ruby file. By commenting out or removing the control lines below, you can run only the controls you find necessary.

require_controls 'bigip-atc' do
  control 'bigip-connectivity'
  control 'bigip-declarative-onboarding'
  control 'bigip-declarative-onboarding-version'
  control 'bigip-application-services'
  control 'bigip-application-services-version'
  control 'bigip-telemetry-streaming'
  control 'bigip-telemetry-streaming-version'
  control 'bigip-licensed'
end

or you can call it at the command line

inspec exec https://github.com/mjmenger/inspec-bigip.git

Please refer to the InSpec documentation for more elaborate variants on these use cases and further use cases not documented here.

The profile uses a set of inputs which can be provided on the command line or with an input file. We listed the necessary inputs below in a sample YAML input file

bigip_address: FQDN or ip address of the BIG-IP to test - this is required
bigip_port: the port for the BIG-IP management service, commonly 443 - this is required
user: the user account with which to authenticate to the BIG-IP - this defaults to admin
password: the password to use to authenticate to the BIG-IP - this is required
do_version: the expected version of declarative onboarding - this is optional
as3_version: the expected version of application services - this is optional
ts_version: the expected version of telemetry streaming - this is optional

Please refer to the InSpec documentation for inputs for more detail