-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
beb47d3
commit 2e61213
Showing
19 changed files
with
317 additions
and
256 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,3 @@ | ||
# terraform-provider-autobotai | ||
Terraform provider for autobotAI (https://autobot.live) | ||
# Documentation | ||
|
||
- [terraform-provider-autobotAI](https://registry.terraform.io/providers/shunyeka-spl/autobotai/latest/docs) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
# Guidance on utilizing autobotAI Integrations, Bot Building Blocks, and Inventory functionalities. | ||
|
||
1. To harness the capabilities of autobotAI Integrations, Bot Building Blocks, and Inventory, follow these steps: | ||
|
||
- Incorporate the API Key and URL into the variable.tf file. | ||
- Inside the relevant folders—such as example/integrations/(aws,azure,gcp,git,ms_teams,conformity,workload_security) or example/bot_building_block/(automation,evaluator,fetcher,listener) or example/inventory/(inventory_schedule)—create a variable.tf file. Include the following contents: | ||
|
||
```hcl | ||
variable "apikey" { | ||
type = string | ||
default = "API Key" | ||
} | ||
variable "url" { | ||
type = string | ||
default = "url" | ||
} | ||
``` | ||
- Configure the essential providers and credentials by creating a provider.tf file. Here's an example setup: | ||
|
||
```hcl | ||
terraform { | ||
required_providers { | ||
autobotai = { | ||
source = "shunyeka-spl/autobotai" | ||
} | ||
} | ||
} | ||
|
||
provider "autobotai" { | ||
apikey = var.apikey | ||
url = var.url | ||
} | ||
``` | ||
- Keep in mind that you can modify the declared values based on your preferences. | ||
2. Execute Terraform operations: | ||
- Navigate to the project directory: | ||
``` | ||
cd /path/terraform-provider-autobotai | ||
``` | ||
- Generate the artifact: | ||
|
||
``` | ||
make install | ||
``` | ||
- Run the Terraform code by moving to the appropriate folder—either example/integrations/, example/bot_building_block/, or example/inventory/: | ||
|
||
``` | ||
cd example/integrations/(aws,azure,gcp,git,ms_teams,conformity,workload_security) | ||
terraform init | ||
terraform apply | ||
``` | ||
|
||
OR | ||
|
||
``` | ||
cd example/bot_building_block/(automation,evaluator,fetcher,listener) | ||
terraform init | ||
terraform apply | ||
``` | ||
|
||
OR | ||
|
||
``` | ||
cd example/inventory/(inventory_schedule) | ||
terraform init | ||
terraform apply | ||
|
||
``` | ||
|
||
|
||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.