Merge pull request #74 from mulesoft-consulting/dev

Preparing V1.4.0

Makefile

@@ -13,6 +13,7 @@ build:
 
 release:
 	GOOS=darwin GOARCH=amd64 go build -o ./bin/${BINARY}_${VERSION}_darwin_amd64
+	GOOS=darwin GOARCH=arm64 go build -o ./bin/${BINARY}_${VERSION}_darwin_arm64
 	GOOS=freebsd GOARCH=386 go build -o ./bin/${BINARY}_${VERSION}_freebsd_386
 	GOOS=freebsd GOARCH=amd64 go build -o ./bin/${BINARY}_${VERSION}_freebsd_amd64
 	GOOS=freebsd GOARCH=arm go build -o ./bin/${BINARY}_${VERSION}_freebsd_arm

README.md

@@ -1,60 +1,62 @@
 # Terraform Provider Anypoint
+
 This is the first terraform provider for anypoint platform! We aim to provide a sustainable tool to automate your actions in anypoint.
 
-This project was initiated by Mulesoft's consultants and architects from the professional team. We welcome any volunteers interested in joining the initiative no matter where you're from ! 
+This project was initiated by Mulesoft's consultants and architects from the professional team. We welcome any volunteers interested in joining the initiative no matter where you're from !
 
 ## How it works
-This provider uses the anypoint platform APIs to perform actions for each one of the implemented resources. 
+
+This provider uses the anypoint platform APIs to perform actions for each one of the implemented resources.
 
 ![alt text](resources/imgs/provider-arch.png)
 
 We use the **anypoint client library** as an abstraction layer to perform actions on the platform.
 
-For better maintainability and in order to speed up the development process, the **anypoint client library** is a library generated from OAS3 specifications written by the community. 
+For better maintainability and in order to speed up the development process, the **anypoint client library** is a library generated from OAS3 specifications written by the community.
 
 The following image describes the delivery cycle:
 
 ![alt text](resources/imgs/provider-deliver.png)
 
-The cycle is composed of 3 steps: 
-  1. Pick one resource and understand how it works using tools like Postman, anypoint's documentation and your favorite browser's inspector. 
+The cycle is composed of 3 steps:
+
+  1. Pick one resource and understand how it works using tools like Postman, anypoint's documentation and your favorite browser's inspector.
   2. Create the OAS3 specification. The specification should at least contain GET, POST and DELETE operations.
   The specification should be contributed [here](https://github.com/mulesoft-consulting/anypoint-automation-client-generator). Using the OAS spec, a go module will be generated and pushed [here](https://github.com/mulesoft-consulting/anypoint-client-go).
-
+  
   ![alt text](resources/imgs/provider-cycle.png)
-
-  3. Implement the resource and related data sources in the provider using the generated library. 
-
+  3. Implement the resource and related data sources in the provider using the generated library.
 
 ## How to use
+
 Run the following command to build the provider
 
 ```bash
-$ go build -o terraform-provider-anypoint
+go build -o terraform-provider-anypoint
 ```
 
-**N.B:** As of Go 1.13 make sure that your `GOPRIVATE` environment variable includes `github.com/mulesoft-consulting` 
+**N.B:** As of Go 1.13 make sure that your `GOPRIVATE` environment variable includes `github.com/mulesoft-consulting`
 
 ```bash
-$ go env -w GOPRIVATE=github.com/mulesoft-consulting
+go env -w GOPRIVATE=github.com/mulesoft-consulting
 ```
 
 ## Test sample configuration
 
 First, build and install the provider.
 
 ```bash
-$ make install
+make install
 ```
 
-Then, navigate inside the `examples` folder, and update your credentials in `main.tf`.   
+Then, navigate inside the `examples` folder, and update your credentials in `main.tf`.
 Run the following command to initialize the workspace and apply the sample configuration.
 
 ```bash
-$ terraform init && terraform apply
+terraform init && terraform apply
 ```
 
-If you prefer to have your credentials in a separate file, create a `params.tfvars.json` file in the `examples` folder. Then add your parameters as shown in the example below: 
+If you prefer to have your credentials in a separate file, create a `params.tfvars.json` file in the `examples` folder. Then add your parameters as shown in the example below:
 
 ```json
 {
@@ -63,64 +65,74 @@ If you prefer to have your credentials in a separate file, create a `params.tfva
   "org_id": "REMPLACE_HERE"
 }
 ```
+
 Make sure to add the params file when you apply your terraform configuration as follow:
+
 ```bash
-$ terraform init && terraform apply -var-file="params.tfvars.json"
+terraform init && terraform apply -var-file="params.tfvars.json"
 ```
 
 ## Debugging mode
+
 First build the project using
+
 ```bash
-$ go build
+go build
 ```
 
-You should have a new file `terraform-provider-anypoint` in the root of the project. To start the provider in debug mode execute the following: 
+You should have a new file `terraform-provider-anypoint` in the root of the project. To start the provider in debug mode execute the following:
+
 ```bash
-$ dlv exec --headless ./terraform-provider-anypoint -- --debug
+dlv exec --headless ./terraform-provider-anypoint -- --debug
 ```
 
 Once executed, connect your debugger (whether it's your IDE or the debugger client) to the debugger server. The following is an example of how to start a client debugger:
+
 ```bash
-$ dlv connect 127.0.0.1:51495
+dlv connect 127.0.0.1:51495
 ```
 
-Then have your client debugger `continue` execution (check the help for more info) then your provider should print something like: 
+Then have your client debugger `continue` execution (check the help for more info) then your provider should print something like:
+
 ```bash
 TF_REATTACH_PROVIDERS='{"anypoint.mulesoft.com/automation/anypoint":{"Protocol":"grpc","Pid":69612,"Test":true,"Addr":{"Network":"unix","String":"/var/folders/yc/k0_j_x0945jdthsw7fzw5ysh0000gp/T/plugin598168131"}}}'
 ```
 
-Now you can run terraform using the debugger, here's an example: 
+Now you can run terraform using the debugger, here's an example:
 
 ```bash
-$ TF_REATTACH_PROVIDERS='{"anypoint.mulesoft.com/automation/anypoint":{"Protocol":"grpc","Pid":69612,"Test":true,"Addr":{"Network":"unix","String":"/var/folders/yc/k0_j_x0945jdthsw7fzw5ysh0000gp/T/plugin598168131"}}}' terraform apply --auto-approve -var-file="params.tfvars.json"
+TF_REATTACH_PROVIDERS='{"anypoint.mulesoft.com/automation/anypoint":{"Protocol":"grpc","Pid":69612,"Test":true,"Addr":{"Network":"unix","String":"/var/folders/yc/k0_j_x0945jdthsw7fzw5ysh0000gp/T/plugin598168131"}}}' terraform apply --auto-approve -var-file="params.tfvars.json"
 ```
 
 ### How to log
-Use `log` package to log. Here's an exampe: 
+
+Use `log` package to log. Here's an exampe:
 
 ```go
 log.Println("[DEBUG] Something happened!")
 ```
 
 ## Documentation
-In order to generate a documentation, we use [tfplugindocs](https://github.com/hashicorp/terraform-plugin-docs).
 
+In order to generate a documentation, we use [tfplugindocs](https://github.com/hashicorp/terraform-plugin-docs).
 
 ## Create Release
-Follow [documentation](https://www.terraform.io/docs/registry/providers/publishing.html#using-goreleaser-locally).
 
+Follow [documentation](https://www.terraform.io/docs/registry/providers/publishing.html#using-goreleaser-locally).
 
 ## How to contribute
-You can contribute by: 
-  * Testing the tool and letting us know of any problems you encounter. 
-  * Contributing specifications for resources [here](https://github.com/mulesoft-consulting/anypoint-automation-client-generator).
-  * Contributing code in the provider itself here. 
 
+You can contribute by:
+
+* Testing the tool and letting us know of any problems you encounter.
+* Contributing specifications for resources [here](https://github.com/mulesoft-consulting/anypoint-automation-client-generator).
+* Contributing code in the provider itself here.
 
 ## Credits
-Made with love. 
 
+Made with love.
+
+## Disclaimer
 
-## Disclaimer 
-**This is an [UNLICENSED software, please review the considerations](UNLICENSE.md).** 
+**This is an [UNLICENSED software, please review the considerations](UNLICENSE.md).**
 This is an open source project, it does not form part of the official MuleSoft product stack, and is therefore not included in MuleSoft support SLAs. Issues should be directed to the community, who will try to assist on a best endeavours basis. This application is distributed **as is**.