The Terraform provider allows you to configure your Bluestone PIM project with infrastructure-as-code principles.
Need support implementing this terraform provider in your organization? Or are you missing features that need to be added, then we are able to offer support. Please contact us at [email protected]
The provider is distributed via the Terraform registry. To use it you need to configure
the required_provider
block. For example:
terraform {
required_providers {
bluestonepim = {
source = "labd/bluestonepim"
# It's recommended to pin the version, e.g.:
# version = "~> 0.0.1"
}
}
}
provider "bluestonepim" {
client_secret = "your mapi client secret (api key)"
}
Clone repository to
Enter the provider directory and build the provider
$ task build-local
A build is created terraform-provider-bluestonepim.0.0
in the root directory
and added to plugin folder available locally:
Use version 99.0.0
in the provider to test your changes locally
terraform {
required_providers {
bluestonepim = {
source = "labd/bluestonepim"
version = "99.0.0"
}
}
}
There are two environment settings for troubleshooting:
TF_LOG=INFO
enables debug output for Terraform.BSP_DEBUG=1
enables debug output to see request/responses to Bluestone PIM
Note this generates a lot of output!
When creating a PR with changes, please include a changie file in the
changelogs/unreleased
folder. This file can be interactively generated by
running changie new
in the root of the project. Pick a suitable category for
the change. We recommend Fixed
or Added
for most cases. See the
changie configuration for the full list of categories.
Once a new version is released all the unreleased changelog files will be merged and added to the general CHANGELOG.md file.
$ task test
$ task coverage
This project is developed by Lab Digital. We welcome additional contributors. Please see our GitHub repository for more information.