jmsperu commented on PR #12900: URL: https://github.com/apache/cloudstack/pull/12900#issuecomment-4522881449
Thanks both — and @weizhouapache, the cron-job suggestion is fair for any deployment with existing ops tooling. The hard mode here is the **first-day greenfield small deployment** where the operator has CloudStack + a NAS and not yet a cron infrastructure; they should be able to opt-in to a unified backup target without standing up a separate process. But that's an opt-in, not a default. I'll push the three-point scope reduction in the next revision: 1. New `infrastructure.backup.include.database` global, **default false** — DB component skipped unless explicitly enabled 2. Docs explicitly recommending the cron-job approach for production 3. Configs + certs path (where there's no realistic alternative) stays as-is, on the same unified NAS target as VM backups If even the opt-in DB path is undesirable (you'd rather we don't ship that code at all and just keep configs+certs), happy to drop it entirely — let me know. Also need to fix the codecov failures — adding unit tests in the next push. -- 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]
