From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Oguz Bektas <o.bektas@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container] setup: make randomize_crontab a state subroutine
Date: Wed, 26 May 2021 11:08:54 +0200 [thread overview]
Message-ID: <543e6e10-4f09-0cc6-3b10-3824f1cc56b9@proxmox.com> (raw)
In-Reply-To: <20210526084816.GA14375@gaia.proxmox.com>
On 26.05.21 10:48, Oguz Bektas wrote:
> On Tue, May 25, 2021 at 03:26:12PM +0200, Thomas Lamprecht wrote:
>> On 25.05.21 15:15, Oguz Bektas wrote:
>>> for consistency in post_create_hook. still works as expected
>>>
>>
>> what's the reason/benefit again?
>
> it looked a bit ugly otherwise with all the other ones being state subs,
> so it's just a style change in the end. anything against this?
no this is not just a style change! You change a method from being a *private*
helper to be a *public* method, and not only that, as this is a plugin "class"
which other modules base off you added that method to the API of the plugin
interface and that without any actual reason!
Rather than asking other to provide reason against changes ask yourself first
what the actual implications are and if there's any actual advantage, which
"looks prettier in my personal perception" seldom counts towards too...
>>
>>> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
>>> ---
>>> src/PVE/LXC/Setup/Base.pm | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/src/PVE/LXC/Setup/Base.pm b/src/PVE/LXC/Setup/Base.pm
>>> index d73335b..be41874 100644
>>> --- a/src/PVE/LXC/Setup/Base.pm
>>> +++ b/src/PVE/LXC/Setup/Base.pm
>>> @@ -422,7 +422,7 @@ sub set_user_authorized_ssh_keys {
>>> $self->ct_modify_file("$home/.ssh/authorized_keys", $ssh_keys, perms => 0700);
>>> }
>>>
>>> -my $randomize_crontab = sub {
>>> +sub randomize_crontab {
>>> my ($self, $conf) = @_;
>>>
>>> my @files;
>>> @@ -450,7 +450,7 @@ my $randomize_crontab = sub {
>>> }
>>> $self->ct_file_set_contents($filename, $new);
>>> }
>>> -};
>>> +}
>>>
>>> sub set_timezone {
>>> my ($self, $conf) = @_;
>>> @@ -493,7 +493,7 @@ sub post_create_hook {
>>>
>>> $self->template_fixup($conf);
>>>
>>> - &$randomize_crontab($self, $conf);
>>> + $self->randomize_crontab($conf);
>>>
>>> $self->set_user_password($conf, 'root', $root_password);
>>> $self->set_user_authorized_ssh_keys($conf, 'root', $ssh_keys) if $ssh_keys;
>>>
>>
prev parent reply other threads:[~2021-05-26 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 13:15 Oguz Bektas
2021-05-25 13:26 ` Thomas Lamprecht
2021-05-26 8:48 ` Oguz Bektas
2021-05-26 9:08 ` Thomas Lamprecht [this message]
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=543e6e10-4f09-0cc6-3b10-3824f1cc56b9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=o.bektas@proxmox.com \
--cc=pve-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