Thank you for taking the time to report this bug and helping to make Ubuntu better.
It would certainly be nice for logrotate to automatically pick up changes to /etc/apache2/envvars in case of local changes, but I'm not sure it's possible to configure logrotate to examine /etc/apache2/envvars at all. I don't see any mechanism in the logrotate configuration file format to do this.
I think it would be reasonable to say that a sysadmin who wants to change the log directory must change all appropriate locations, including /etc/logrotate.d/apache2, as part of the interface currently provided by packaging.
So while it would be nice for this to be automatic somehow, I think this a wishlist item as that is not the current interface. It's additionally complex to arrange without an existing mechanism for logrotate to dynamically peek into other packages' configuration files as part of its own configuration.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
It would certainly be nice for logrotate to automatically pick up changes to /etc/apache2/ envvars in case of local changes, but I'm not sure it's possible to configure logrotate to examine /etc/apache2/ envvars at all. I don't see any mechanism in the logrotate configuration file format to do this.
I think it would be reasonable to say that a sysadmin who wants to change the log directory must change all appropriate locations, including /etc/logrotate. d/apache2, as part of the interface currently provided by packaging.
So while it would be nice for this to be automatic somehow, I think this a wishlist item as that is not the current interface. It's additionally complex to arrange without an existing mechanism for logrotate to dynamically peek into other packages' configuration files as part of its own configuration.