Rename project into arduino-cloud-cli

Author: polldo

.gitignore

@@ -1,5 +1,5 @@
 # Compilation artifacts
-iot-cloud-cli
+arduino-cloud-cli
 
 # Configuration file
 config.yaml

README.md

@@ -1,10 +1,10 @@
-# iot-cloud-cli
+# arduino-cloud-cli
 
-iot-cloud-cli is a command line interface that allows to exploit the features of Arduino IoT Cloud. As of now, it is possible to provision a device.
+arduino-cloud-cli is a command line interface that allows to exploit the features of Arduino IoT Cloud. As of now, it is possible to provision a device.
 
 ### Requirements
 
-This is all you need to use iot-cloud-cli for device **provisioning**:
+This is all you need to use arduino-cloud-cli for device **provisioning**:
  * A client ID and a secret ID, retrievable from the [cloud](https://create.arduino.cc/iot/integrations) by creating a new API key
  * The folder containing the precompiled provisioning firmwares (`binaries`) needs to be in the same location you run the command from
 
@@ -17,101 +17,101 @@ However, if the verbose flag `-v` is used, then the behaviour will change: the l
 As an example, let's take the `device create`command. We want to save the information of the newly created device in a file.
 So we simply lunch the command:
 
-`$ iot-cloud-cli device create --name mydevice --format json > mydevice.json`
+`$ arduino-cloud-cli device create --name mydevice --format json > mydevice.json`
 
 The resulting mydevice.json will only contain device information in a json format.
 
 Another example: let's say that the execution of the previous command results in an error. In that case the json file will be empty and the terminal will print out the error. Now we want to execute again the command with the logs enabled, in order to understand the issue. So we execute the following:
 
-`$ iot-cloud-cli device create --name mydevice -v`
+`$ arduino-cloud-cli device create --name mydevice -v`
 
 
 ## Set a configuration
 
-iot-cloud-cli needs a configuration file to be used. At the moment, the configuration file should be contained in the same directory where the cli commands are executed.
+arduino-cloud-cli needs a configuration file to be used. At the moment, the configuration file should be contained in the same directory where the cli commands are executed.
 The configuration file contains the Arduino IoT Cloud client ID and its corresponding secret.
 You can retrieve them from the [cloud](https://create.arduino.cc/iot/integrations) by creating a new API key.
 
 Once you have the IDs, call this command to init a new configuration file:
 
-`$ iot-cloud-cli config init`
+`$ arduino-cloud-cli config init`
 
 A file named `arduino-cloud.yaml` will be created in the current working directory. 
 Then you should open such file and replace the client and secret placeholders with the value you previously retrieved.
 
 
 To create a configuration file in a different folder, use this command:
 
-`$ iot-cloud-cli config init --dest-dir <destinationFolder>`
+`$ arduino-cloud-cli config init --dest-dir <destinationFolder>`
 
 To reset an old configuration file, just overwrite it using this command:
 
-`$ iot-cloud-cli config init --overwrite`
+`$ arduino-cloud-cli config init --overwrite`
 
 Configuration file is supported in two different format: json and yaml. Use the `--config-format` to choose it. Default is yaml.
 
-`$ iot-cloud-cli config init --config-format json`
+`$ arduino-cloud-cli config init --config-format json`
 
 ## Device provisioning
 
 When provisioning a device, you can optionally specify the port to which the device is connected to and its fqbn. If they are not given, then the first device found will be provisioned.
 
 Use this command to provision a device:
 
-`$ iot-cloud-cli device create --name <deviceName> --port <port> --fqbn <deviceFqbn>`
+`$ arduino-cloud-cli device create --name <deviceName> --port <port> --fqbn <deviceFqbn>`
 
 ## Device commands
 
 Once a device has been created thorugh the provisioning procedure, it can be deleted by using the following command:
-`$ iot-cloud-cli device delete --id <deviceID>`
+`$ arduino-cloud-cli device delete --id <deviceID>`
 
 Devices currently present on Arduino IoT Cloud can be retrieved by using this command:
-`$ iot-cloud-cli device list`
+`$ arduino-cloud-cli device list`
 
 ## Thing commands
 
 Things can be created starting from a template or by cloning another thing.
 
 Create a thing from a thing template. Supported template formats are JSON and YAML. The name parameter is optional. If it is provided then it overrides the name retrieved from the template:
 
-`$ iot-cloud-cli thing create --name <thingName> --template <template.(json|yaml)>`
+`$ arduino-cloud-cli thing create --name <thingName> --template <template.(json|yaml)>`
 
 Create a thing by cloning another thing, here the *name is mandatory*:
 
-`$ iot-cloud-cli thing clone --name <thingName> --clone-id <thingToCloneID>`
+`$ arduino-cloud-cli thing clone --name <thingName> --clone-id <thingToCloneID>`
 
 
 Things can be printed thanks to a list command. 
 
 Print a list of available things and their variables by using this command:
 
-`$ iot-cloud-cli thing list --show-variables`
+`$ arduino-cloud-cli thing list --show-variables`
 
 Print a *filtered* list of available things, print only things belonging to the ids list:
 
-`$ iot-cloud-cli thing list --ids <thingOneID>,<thingTwoID>`
+`$ arduino-cloud-cli thing list --ids <thingOneID>,<thingTwoID>`
 
 Print only the thing associated to the passed device:
 
-`$ iot-cloud-cli thing list --device-id <deviceID>`
+`$ arduino-cloud-cli thing list --device-id <deviceID>`
 
 Delete a thing with the following command:
 
-`$ iot-cloud-cli thing delete --device-id <deviceID>`
+`$ arduino-cloud-cli thing delete --device-id <deviceID>`
 
 Extract a template from an existing thing. The template can be saved in two formats: json or yaml. The default format is yaml:
 
-`$ iot-cloud-cli thing extract --id <thingID> --outfile <templateFile> --format <yaml|json>`
+`$ arduino-cloud-cli thing extract --id <thingID> --outfile <templateFile> --format <yaml|json>`
 
 Bind a thing to an existing device:
 
-`$ iot-cloud-cli thing bind --id <thingID> --device-id <deviceID>`
+`$ arduino-cloud-cli thing bind --id <thingID> --device-id <deviceID>`
 
 ## Ota commands
 
 Perform an OTA firmware update. Note that the binary file (`.bin`) should be compiled using an arduino core that supports the specified device.
 The default OTA upload should complete in 10 minutes. Use `--deferred` flag to extend this time to one week.
 
-`$ iot-cloud-cli ota upload --device-id <deviceID> --file <sketch-file.ino.bin>`
+`$ arduino-cloud-cli ota upload --device-id <deviceID> --file <sketch-file.ino.bin>`
 
-`$ iot-cloud-cli ota upload --device-id <deviceID> --file <sketch-file.ino.bin> --deferred`
+`$ arduino-cloud-cli ota upload --device-id <deviceID> --file <sketch-file.ino.bin> --deferred`

arduino/cli/commander.go

@@ -11,7 +11,7 @@ import (
 	"github.com/arduino/arduino-cli/commands/upload"
 	"github.com/arduino/arduino-cli/configuration"
 	rpc "github.com/arduino/arduino-cli/rpc/cc/arduino/cli/commands/v1"
-	"github.com/arduino/iot-cloud-cli/arduino"
+	"github.com/arduino/arduino-cloud-cli/arduino"
 	"github.com/sirupsen/logrus"
 )
 

arduino/grpc/client.go

@@ -8,7 +8,7 @@ import (
 
 	rpc "github.com/arduino/arduino-cli/rpc/cc/arduino/cli/commands/v1"
 	"github.com/arduino/arduino-cli/rpc/cc/arduino/cli/settings/v1"
-	"github.com/arduino/iot-cloud-cli/arduino"
+	"github.com/arduino/arduino-cloud-cli/arduino"
 	"google.golang.org/grpc"
 )
 

cli/cli.go

@@ -8,10 +8,10 @@ import (
 
 	"github.com/arduino/arduino-cli/cli/errorcodes"
 	"github.com/arduino/arduino-cli/cli/feedback"
-	"github.com/arduino/iot-cloud-cli/cli/config"
-	"github.com/arduino/iot-cloud-cli/cli/device"
-	"github.com/arduino/iot-cloud-cli/cli/ota"
-	"github.com/arduino/iot-cloud-cli/cli/thing"
+	"github.com/arduino/arduino-cloud-cli/cli/config"
+	"github.com/arduino/arduino-cloud-cli/cli/device"
+	"github.com/arduino/arduino-cloud-cli/cli/ota"
+	"github.com/arduino/arduino-cloud-cli/cli/thing"
 	"github.com/sirupsen/logrus"
 	"github.com/spf13/cobra"
 )

cli/config/init.go

@@ -5,7 +5,7 @@ import (
 
 	"github.com/arduino/arduino-cli/cli/errorcodes"
 	"github.com/arduino/arduino-cli/cli/feedback"
-	"github.com/arduino/iot-cloud-cli/command/config"
+	"github.com/arduino/arduino-cloud-cli/command/config"
 	"github.com/sirupsen/logrus"
 	"github.com/spf13/cobra"
 )

cli/device/create.go

@@ -6,7 +6,7 @@ import (
 
 	"github.com/arduino/arduino-cli/cli/errorcodes"
 	"github.com/arduino/arduino-cli/cli/feedback"
-	"github.com/arduino/iot-cloud-cli/command/device"
+	"github.com/arduino/arduino-cloud-cli/command/device"
 	"github.com/sirupsen/logrus"
 	"github.com/spf13/cobra"
 )

cli/device/delete.go

@@ -5,7 +5,7 @@ import (
 
 	"github.com/arduino/arduino-cli/cli/errorcodes"
 	"github.com/arduino/arduino-cli/cli/feedback"
-	"github.com/arduino/iot-cloud-cli/command/device"
+	"github.com/arduino/arduino-cloud-cli/command/device"
 	"github.com/sirupsen/logrus"
 	"github.com/spf13/cobra"
 )

cli/device/list.go

@@ -6,7 +6,7 @@ import (
 	"github.com/arduino/arduino-cli/cli/errorcodes"
 	"github.com/arduino/arduino-cli/cli/feedback"
 	"github.com/arduino/arduino-cli/table"
-	"github.com/arduino/iot-cloud-cli/command/device"
+	"github.com/arduino/arduino-cloud-cli/command/device"
 	"github.com/sirupsen/logrus"
 	"github.com/spf13/cobra"
 )

cli/ota/upload.go

@@ -5,7 +5,7 @@ import (
 
 	"github.com/arduino/arduino-cli/cli/errorcodes"
 	"github.com/arduino/arduino-cli/cli/feedback"
-	"github.com/arduino/iot-cloud-cli/command/ota"
+	"github.com/arduino/arduino-cloud-cli/command/ota"
 	"github.com/sirupsen/logrus"
 	"github.com/spf13/cobra"
 )