From: Gabriel Goller <g.goller@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH cluster 2/3] add consent-text paramter to datacenter config file
Date: Wed, 4 Dec 2024 10:16:49 +0100 [thread overview]
Message-ID: <5vjnedsr2m26s6ijmuhalowo3uma3f4gbw7r3syetzn2fufovf@hltd47ok6oon> (raw)
In-Reply-To: <be525e35-374a-45f8-ad10-b74adae49556@proxmox.com>
On 03.12.2024 18:24, Thomas Lamprecht wrote:
>Am 03.12.24 um 16:29 schrieb Gabriel Goller:
>> The consent-text paramter is the base64-encoded content of the optional
>> consent-banner which can be displayed before login.
>
>This can get quite big, would be good to set some relatively high limit here,
>I think, as our pmxcfs files have a max size and not being able to change other
>options due to this property being close to the pmxcfs file size limit would
>not be ideal.
To keep the textareafield widget generic, I would add the maxLength
parameters to pbs and pve separately.
About the limit itself, the example banner in the bug report [0] has 500
characters and these legal texts can sometimes get quite long – so maybe
a limit of 1000 characters?
[0]: https://bugzilla.proxmox.com/show_bug.cgi?id=5463
>btw. Did we ever talk about placing this into a dedicated, separate file?
>(just out of interest, might be also an option to consider here if we did
>not talked already about it)
Yep, my first version used a separate file – this was discussed here:
https://lore.proxmox.com/pbs-devel/fc22ec23-a300-488d-821f-bea1285881a8@proxmox.com/
>>
>> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
>> ---
>> src/PVE/DataCenterConfig.pm | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/src/PVE/DataCenterConfig.pm b/src/PVE/DataCenterConfig.pm
>> index abd0bbfd4532..0347bd5ae19f 100644
>> --- a/src/PVE/DataCenterConfig.pm
>> +++ b/src/PVE/DataCenterConfig.pm
>> @@ -449,6 +449,11 @@ my $datacenter_schema = {
>> pattern => "(?:${PVE::JSONSchema::PVE_TAG_RE};)*${PVE::JSONSchema::PVE_TAG_RE}",
>> typetext => "<tag>[;<tag>...]",
>> },
>> + 'consent-text' => {
>> + optional => 1,
>> + type => 'string',
>> + description => "Consent text that is displayed before logging in."
>> + },
>> },
>> };
>>
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-12-04 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 15:29 [pve-devel] [PATCH cluster/docs/manager 0/3] fix #5463: add optional Consent Banner on login Gabriel Goller
2024-12-03 15:29 ` [pve-devel] [PATCH manager 1/3] show optional consent-banner before login Gabriel Goller
2024-12-03 17:24 ` Thomas Lamprecht
2024-12-04 8:48 ` Gabriel Goller
2024-12-03 15:29 ` [pve-devel] [PATCH cluster 2/3] add consent-text paramter to datacenter config file Gabriel Goller
2024-12-03 17:24 ` Thomas Lamprecht
2024-12-04 9:16 ` Gabriel Goller [this message]
2024-12-04 10:16 ` Thomas Lamprecht
2024-12-05 10:45 ` Gabriel Goller
2024-12-03 15:29 ` [pve-devel] [PATCH docs 3/3] add consent-banner description Gabriel Goller
2024-12-06 11:19 ` [pve-devel] [PATCH cluster/docs/manager 0/3] fix #5463: add optional Consent Banner on login Gabriel Goller
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=5vjnedsr2m26s6ijmuhalowo3uma3f4gbw7r3syetzn2fufovf@hltd47ok6oon \
--to=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.