apiclient: add network configure subcommand

Implements 'apiclient network configure <input-source>' to enable runtime
network configuration for Bottlerocket. Supports file://, base64: input
sources with client-side URI processing. Content is sent to the API server
for further processing.

Signed-off-by: Yutong Sun <yutongsu@amazon.com>

Author: ytsssun

sources/api/apiclient/README.md

@@ -5,7 +5,7 @@ Current version: 0.1.0
 ## apiclient binary
 
 The `apiclient` binary provides high-level methods to interact with the Bottlerocket API.
-There's a [set](#set-mode) subcommand for changing settings, an [update](#update-mode) subcommand for updating the host, and an [exec](#exec-mode) subcommand for running commands in host containers.
+There's a [set](#set-mode) subcommand for changing settings, a [network configure](#network-configure) subcommand for configuring network settings, an [update](#update-mode) subcommand for updating the host, and an [exec](#exec-mode) subcommand for running commands in host containers.
 There's also a low-level [raw](#raw-mode) subcommand for direct interaction with the HTTP API.
 
 It talks to the Bottlerocket socket by default.
@@ -75,6 +75,53 @@ You can use JSON form to set it:
 apiclient set --json '{"motd": "42"}'
 ```
 
+### Network configure
+
+This allows you to configure network settings by providing a net.toml file which netdog uses for network configuration.
+The configuration is written to `/.bottlerocket/net.toml` and will be validated and applied at the next boot by netdog.
+
+The network configure command accepts input from different sources using URI schemes:
+
+#### File URI input
+
+You can specify a local file path using the `file://` URI scheme:
+
+```shell
+apiclient network configure file:///path/to/net.toml
+```
+
+#### Base64 encoded input
+
+For inline configuration, you can provide base64-encoded content:
+
+```shell
+apiclient network configure base64:dmVyc2lvbiA9IDIKCltldGgwXQpkaGNwNCA9IHRydWU=
+```
+
+This is particularly useful for automation and configuration management where you want to embed the network configuration directly in scripts or user data.
+
+#### Configuration format
+
+The net.toml file uses the same format that netdog supports. Here's an example:
+
+```toml
+version = 2
+
+[eth0]
+dhcp4 = true
+dhcp6 = false
+
+[eth1]
+static4 = ["192.168.1.100/24"]
+route = [{to = "default", via = "192.168.1.1"}]
+```
+
+After configuring the network settings, you'll need to reboot the system for the changes to take effect:
+
+```shell
+apiclient reboot
+```
+
 ### Update mode
 
 To start, you can check what updates are available:
@@ -329,7 +376,7 @@ The results from each item in the report will be one of:
 ## apiclient library
 
 The apiclient library provides high-level methods to interact with the Bottlerocket API.  See
-the documentation for submodules [`apply`], [`exec`], [`get`], [`reboot`], [`report`], [`set`],
+the documentation for submodules [`apply`], [`exec`], [`get`], [`network`], [`reboot`], [`report`], [`set`],
 and [`update`] for high-level helpers.
 
 For more control, and to handle APIs without high-level wrappers, there are also 'raw' methods

sources/api/apiclient/README.tpl

@@ -5,7 +5,7 @@ Current version: {{version}}
 ## apiclient binary
 
 The `apiclient` binary provides high-level methods to interact with the Bottlerocket API.
-There's a [set](#set-mode) subcommand for changing settings, an [update](#update-mode) subcommand for updating the host, and an [exec](#exec-mode) subcommand for running commands in host containers.
+There's a [set](#set-mode) subcommand for changing settings, a [network configure](#network-configure) subcommand for configuring network settings, an [update](#update-mode) subcommand for updating the host, and an [exec](#exec-mode) subcommand for running commands in host containers.
 There's also a low-level [raw](#raw-mode) subcommand for direct interaction with the HTTP API.
 
 It talks to the Bottlerocket socket by default.
@@ -75,6 +75,53 @@ You can use JSON form to set it:
 apiclient set --json '{"motd": "42"}'
 ```
 
+### Network configure
+
+This allows you to configure network settings by providing a net.toml file which netdog uses for network configuration.
+The configuration is written to `/.bottlerocket/net.toml` and will be validated and applied at the next boot by netdog.
+
+The network configure command accepts input from different sources using URI schemes:
+
+#### File URI input
+
+You can specify a local file path using the `file://` URI scheme:
+
+```shell
+apiclient network configure file:///path/to/net.toml
+```
+
+#### Base64 encoded input
+
+For inline configuration, you can provide base64-encoded content:
+
+```shell
+apiclient network configure base64:dmVyc2lvbiA9IDIKCltldGgwXQpkaGNwNCA9IHRydWU=
+```
+
+This is particularly useful for automation and configuration management where you want to embed the network configuration directly in scripts or user data.
+
+#### Configuration format
+
+The net.toml file uses the same format that netdog supports. Here's an example:
+
+```toml
+version = 2
+
+[eth0]
+dhcp4 = true
+dhcp6 = false
+
+[eth1]
+static4 = ["192.168.1.100/24"]
+route = [{to = "default", via = "192.168.1.1"}]
+```
+
+After configuring the network settings, you'll need to reboot the system for the changes to take effect:
+
+```shell
+apiclient reboot
+```
+
 ### Update mode
 
 To start, you can check what updates are available:

sources/api/apiclient/src/lib.rs

@@ -1,5 +1,5 @@
 //! The apiclient library provides high-level methods to interact with the Bottlerocket API.  See
-//! the documentation for submodules [`apply`], [`exec`], [`get`], [`reboot`], [`report`], [`set`],
+//! the documentation for submodules [`apply`], [`exec`], [`get`], [`network`], [`reboot`], [`report`], [`set`],
 //! and [`update`] for high-level helpers.
 //!
 //! For more control, and to handle APIs without high-level wrappers, there are also 'raw' methods
@@ -23,6 +23,7 @@ pub mod apply;
 pub mod ephemeral_storage;
 pub mod exec;
 pub mod get;
+pub mod network;
 pub mod reboot;
 pub mod report;
 pub mod set;