terraform-provider-onefuse's Introduction

Terraform Provider for OneFuse

Terraform Provider for integrating with OneFuse.

Requirements

Terraform 0.13.x
Go >= 1.14 (to build the provider plugin)

Note: Onefuse will drop support for Terraform 0.12.x after the release of Terraform Provider for OneFuse 1.0.1.

Building the provider

Clone repository to: $GOPATH/src/github.com/cloudboltsoftware/terraform-provider-onefuse

$ mkdir -p $GOPATH/src/github.com/CloudBoltSoftware
$ cd $GOPATH/src/github.com/CloudBoltSoftware
$ git clone https://github.com/CloudBoltSoftware/terraform-provider-onefuse.git

Enter the provider directory and install the provider's dependencies

$ cd $GOPATH/src/github.com/CloudBoltSoftware/terraform-provider-onefuse.git
$ make install

To build the provider binary, create the $HOME/.terraform.d/plugins/ directory and run the make install command:

$ make build
$ mkdir $HOME/.terraform.d/plugins/
$ mv terraform-provider-onefuse_v* $HOME/.terraform.d/plugins/

Then copy the binary to your terraform plugins directory

You may want to use Make 4.3+ to ensure all make features work.

Using the provider

Sample Terraform Configuration

To get started with the Terraform Provider for OneFuse, put the following into a file called main.tf.

Fill in the provider "onefuse" section with details about your OneFuse instance.

provider "onefuse" {
  address     = "localhost"
  port        = "8000"
  user        = "admin"
  password    = "my-password"
  scheme      = "https"
  verify_ssl  = false
}

resource "onefuse_naming" "my-onefuse-name" {
  naming_policy_id        = "2"
  dns_suffix              = "company.com"
  workspace_id            = "6"
  template_properties     = {
      "ownerName"               = "[email protected]"
      "Environment"             = "dev"
      "OS"                      = "Linux"
      "Application"             = "Web Servers"
      "suffix"                  = "company.com"
      "tenant"                  =  "mytenant"
  }
}

Releases

To learn more, please visit our docs

v1.1

October 14, 2020

OneFuse DNS module support
OneFuse IPAM module support
OneFuse Microsoft Active Directory module support

v1.0

July 15, 2020

OneFuse Naming module support

Contributing

Interested in contributing? Wonderful!

If you spot a problem, or room for improvement, please create an issue.
If you are interested in fixing an issue, please make a pull request.
A CloudBolt Developer will review your submission within a few days.

For more information about contributing to Terraform Provider Onefuse, see CONTRIBUTING.md.

License

Terraform Provider Onefuse is licensed under Mozilla Public License 2.0. For more information see LICENSE

terraform-provider-onefuse's People

Contributors

Stargazers

Watchers

terraform-provider-onefuse's Issues

Support nested objects in `template_properties`

template_properties in the provider can only support key(string):value(string) pairs. The backing API can support key(string):value(any) pairs, like this:

{
    "someKey": {
        "nestedValue": ["thing", "thing", "thing"]
    },
    "someOtherKey": "value",
    "finallyKey": ["stuff"]
}

To support arbitrary key:value pairs we need to change template_properties from a Terraform Map to a String of JSON. Similar to how the aws_iam_policy resource does things: reference.

This is a breaking change so we're not going to make it lightly. If you have concerns about this change let us know. If necessary, we will support two workflows for a while with a deprecation period for the old map-based template_properties.

Recommend Projects

cloudboltsoftware / terraform-provider-onefuse Goto Github PK