Skip to content

Latest commit

 

History

History
60 lines (37 loc) · 2.81 KB

README.md

File metadata and controls

60 lines (37 loc) · 2.81 KB
Raw

Actions Status Slack NPM version Python version NuGet version PkgGoDev License

F5 BigIP Provider

This provider allows management of F5 BigIP resources using Pulumi. This provider uses the iControlREST API to perform management tasks, so it will need to be installed and enabled on your F5 device before proceeding.

Installing

This package is available in many languages in the standard packaging formats.

Node.js (Java/TypeScript)

To use from JavaScript or TypeScript in Node.js, install using either npm:

$ npm install @pulumi/f5bigip

or yarn:

$ yarn add @pulumi/f5bigip

Python

To use from Python, install using pip:

$ pip install pulumi_f5bigip

Go

To use from Go, use go get to grab the latest version of the library

$ go get github.com/pulumi/pulumi-f5bigip/sdk/v3

.NET

To use from .NET, install using dotnet add package:

$ dotnet add package Pulumi.F5bigip

Configuration

The following configuration points are available:

  • f5bigip:address - Domain name/IP of the BigIP. May be set via the BIGIP_HOST environment variable.
  • f5bigip:port - Management Port to connect to BigIP.
  • f5bigip:username - Username with API access to the BigIP. May be set via the BIGIP_USER environment variable.
  • f5bigip:password - Password for API access to the BigIP. May be set via the BIGIP_PASSWORD environment variable.
  • f5bigip:tokenAuth - Enable to use an external authentication source (LDAP, TACACS, etc). May be set via the BIGIP_TOKEN_AUTH environment variable.
  • f5bigip:tokenAuth - Enable to use an external authentication source (LDAP, TACACS, etc). May be set via the BIGIP_TOKEN_AUTH environment variable.
  • f5bigip:loginRef - Login reference for token authentication (see BIG-IP REST docs for details) May be set via the BIGIP_LOGIN_REF environment variable.

Reference

For further information, please visit the F5bigip provider docs or for detailed reference documentation, please visit the API docs.