pub struct NetworkVolumeUpdateInput {
pub name: Option<String>,
pub size: Option<u32>,
}Expand description
Input parameters for updating an existing network volume.
This struct allows you to modify the name and/or size of an existing network volume. Both fields are optional, allowing you to update only the properties you want to change.
§Important Notes
- Size expansion only: You can increase the volume size but never decrease it
- Live expansion: Size changes can be performed while Pods are using the volume
- Billing impact: Size increases affect billing immediately
- No downtime: Name changes are instantaneous with no service interruption
§Validation Requirements
- name: If provided, must be 1-255 characters long
- size: If provided, must be larger than current size and ≤4,000 GB
§Examples
use runpod_sdk::model::NetworkVolumeUpdateInput;
// Only change the name
let rename_only = NetworkVolumeUpdateInput {
name: Some("renamed-volume".to_string()),
size: None,
};
// Only expand the size from current to 500GB
let expand_only = NetworkVolumeUpdateInput {
name: None,
size: Some(500),
};
// Change both name and size
let full_update = NetworkVolumeUpdateInput {
name: Some("production-storage-v2".to_string()),
size: Some(1000),
};
// No changes (useful for testing API connectivity)
let no_change = NetworkVolumeUpdateInput::default();Fields§
§name: Option<String>Optional new name for the network volume.
If provided, the volume will be renamed to this value. The name change is applied immediately and does not affect volume availability or performance.
Constraints:
- Length: 1-255 characters (if provided)
- Allowed characters: letters, numbers, spaces, hyphens, underscores
- Case-sensitive
Use cases:
- Updating naming conventions across your infrastructure
- Adding version numbers or status indicators
- Improving organization and searchability
Note: Set to None to keep the current name unchanged.
size: Option<u32>Optional new size for the network volume in gigabytes (GB).
If provided, the volume will be expanded to this new size. The expansion operation preserves all existing data and can be performed while Pods are actively using the volume.
Constraints:
- Must be larger than the current volume size (expansion only)
- Maximum: 4,000 GB (4 TB)
- Minimum increment: 1 GB
Process:
- API call returns immediately with success
- Volume expansion happens asynchronously in the background
- Additional capacity becomes available once expansion completes
- Billing for the new size begins immediately
Performance impact:
- No downtime during expansion
- File system may need manual extension in some cases
- Larger volumes may have improved IOPS performance
Note: Set to None to keep the current size unchanged.
Trait Implementations§
Source§impl Clone for NetworkVolumeUpdateInput
impl Clone for NetworkVolumeUpdateInput
Source§fn clone(&self) -> NetworkVolumeUpdateInput
fn clone(&self) -> NetworkVolumeUpdateInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more