zmuxuny commented on issue #4497: URL: https://github.com/apache/rocketmq-dashboard/issues/4497#issuecomment-5719276872
Audit status update: the provider-field design and the tested prototype remain useful for review, but commit `541fff679eee15875aed75f32da8fd7e05690f52` should **not** be opened as an upstream PR unchanged. Since that prototype was built, adjacent correctness fixes established two contracts that the feature branch must absorb before submission: - Aliyun settings reads/mutations need the business-level `success` validation used by the current Aliyun provider/catalog paths (#4504/#4507), so a normally completed OpenAPI failure cannot become valid-looking settings data. - The Apache settings path must retain the all-Broker pre-read boundary from #4542; rebasing the feature must not restore the earlier read-one/write-one partial-update window. If the provider field matrix/API scope is accepted, I will first rebase the prototype onto current `master`, apply those contracts, and rerun the backend/provider/controller and cloud UI suites before opening the PR. The issue's proposed capability/editable-fields design is unchanged. -- 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]
