From: Hannes Laimer <h.laimer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox v4 1/3] pbs-api-types: allow traffic-control rules to match users
Date: Wed, 12 Nov 2025 11:35:00 +0100 [thread overview]
Message-ID: <20251112103505.122844-2-h.laimer@proxmox.com> (raw)
In-Reply-To: <20251112103505.122844-1-h.laimer@proxmox.com>
Extend traffic-control rules with an optional list of user IDs so
API traffic can be limited per user in addition to IP-based rules.
Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
Reviewed-by: Christian Ebner <c.ebner@proxmox.com>
Tested-by: Christian Ebner <c.ebner@proxmox.com>
---
pbs-api-types/src/traffic_control.rs | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/pbs-api-types/src/traffic_control.rs b/pbs-api-types/src/traffic_control.rs
index 2a359eda..174f53a2 100644
--- a/pbs-api-types/src/traffic_control.rs
+++ b/pbs-api-types/src/traffic_control.rs
@@ -5,6 +5,7 @@ use proxmox_schema::{api, ApiType, Schema, StringSchema, Updater};
use proxmox_schema::api_types::CIDR_SCHEMA;
+use crate::Userid;
use crate::{DAILY_DURATION_FORMAT, PROXMOX_SAFE_ID_FORMAT, SINGLE_LINE_COMMENT_SCHEMA};
pub const TRAFFIC_CONTROL_TIMEFRAME_SCHEMA: Schema =
@@ -125,6 +126,11 @@ pub struct ClientRateLimitConfig {
},
optional: true,
},
+ users: {
+ type: Array,
+ items: { type: Userid },
+ optional: true,
+ },
},
)]
#[derive(Clone, Serialize, Deserialize, PartialEq, Updater)]
@@ -146,6 +152,9 @@ pub struct TrafficControlRule {
/// Enable the rule at specific times
#[serde(skip_serializing_if = "Option::is_none")]
pub timeframe: Option<Vec<String>>,
+ /// Rule applies to authenticated API requests of any of these users (overrides IP-only rules)
+ #[serde(skip_serializing_if = "Option::is_none")]
+ pub users: Option<Vec<Userid>>,
}
#[api(
--
2.47.3
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-11-12 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 10:34 [pbs-devel] [PATCH proxmox{, -backup} v4 0/6] add user specific rate-limits Hannes Laimer
2025-11-12 10:35 ` Hannes Laimer [this message]
2025-11-12 10:35 ` [pbs-devel] [PATCH proxmox v4 2/3] http: track user tag updates on rate-limited streams Hannes Laimer
2025-11-12 10:35 ` [pbs-devel] [PATCH proxmox v4 3/3] rest-server: propagate rate-limit tags from authenticated users Hannes Laimer
2025-11-12 10:35 ` [pbs-devel] [PATCH proxmox-backup v4 1/3] api: taffic-control: update/delete users on rule correctly Hannes Laimer
2025-11-12 10:35 ` [pbs-devel] [PATCH proxmox-backup v4 2/3] traffic-control: add user-specific rule matching and precedence Hannes Laimer
2025-11-12 10:35 ` [pbs-devel] [PATCH proxmox-backup v4 3/3] ui: traffic-control: add users field in edit form and list Hannes Laimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251112103505.122844-2-h.laimer@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox