brianloss commented on pull request #420: URL: https://github.com/apache/fluo-muchos/pull/420#issuecomment-996020995
> > there is not a more recent version > > of CentOS 7.9 for Azure > > New instances can be created by users and there's no requirement to use CentOS 7.9. I don't think the fact that nobody has yet created an updated one is a compelling override to what was previously discussed in #408 and #411. Somebody can create one at any time, or use another instance in their config. Or, they can customize their cloud-config file to update, if they prefer that method. But, I don't think it should be the default. The crux of the problem in my mind is the default configuration that is checked in will not deploy on Azure. What @arvindshmicrosoft has put here is a change that only affects the Azure use case. Since we don't have anyone that wants to take on the task of building a CentOS image, publishing it to the marketplace, and maintaining it there (which effectively means there is no option to use a newer image), I think it makes sense to update the packages in the existing image at deploy time. Since the packages are so far out of date that the CA certs aren't new enough to verify Apache servers, I believe it makes good security sense to update all packages. Maybe that cloud-init config file could be a template so the update packages defaults to `true` so that an out-of-the box setup will deploy, but if a user wants to use their own image and skip package updates, they could change just the configuration in the conf file to disable the update? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
