chef-server
chef-server copied to clipboard
Clarify frontend upgrades
Frontends don't need to worry about database vacuuming or reindexing
Signed-off-by: Sean Horn [email protected]
Description
Frontend upgrades in a Chef Backend are just normal. No database work needed there
Issues Resolved
https://getchef.zendesk.com/agent/tickets/29889
Check List
- [ ] New functionality includes tests
- [ ] All buildkite tests pass
- [ ] Full omnibus build and tests in buildkite pass
- [X] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/main/CONTRIBUTING.md#developer-certification-of-origin-dco
- [ ] PR title is a worthy inclusion in the CHANGELOG
Deploy Preview for chef-server processing.
Name | Link |
---|---|
Latest commit | 80f29fe443a1bdd28399ee00a2f1e5fed3b9019d |
Latest deploy log | https://app.netlify.com/sites/chef-server/deploys/62a38261f5a7b40008119bb7 |
Yes, thanks for the updates, @IanMadd @PrajaktaPurohit
This looks good for a merge to me.
Alright, I started on main from about 15 minutes ago, then force pushed to my branch to fold all the commits into one.
The DCO is now present on the single commit, 1330bd
Please merge.
Alright, I started on main from about 15 minutes ago, then force pushed to my branch to fold all the commits into one.
The DCO is now present on the single commit, 1330bd7
Please merge.
80f29fe also includes the DCO. Please merge