Models used:

• GPT 5.5 (Codex, from JetBrains PyCharm) for the schema generation and the tests
• Qwen 3.8 for code review

I wonder if T1681 couldn't host them too. If so:

Patch written to test Codex. Model: GPT-5.5 (High).

Remove unused uids

Improve comment

Actually rewrite the file too

Avoid too many blank lines in Markdown rendering

Improve description

Revert to the cnf.sls context-variable version per dereckson: easier to see which values are configurable/pillar-dependant in roles/*.sls than in configuration templates.

No please revert back to the version with innodb_buffer_pool_size = {{ innodb_buffer_pool_size }}.

Address dereckson feedback: drop the innodb_buffer_pool_size context var in cnf.sls and access pillar["dbserver_mysql"]["server"]["innodb_buffer_pool_size"] directly in server.cnf instead, so it fails loudly if the server pillar block is missing rather than silently falling back via pillar.get.

That will be useful to implement a bunch of values for T2337

I confirm we probably don't need it on WindRiver right now.

Tested, works fine.

Merge the three exact-match redirect blocks (/cd, /cd/, /cd/dashboard) into a single regex location, as suggested.

Merge the three exact-match redirect blocks (/cd, /cd/, /cd/dashboard) into a single regex location, as suggested: location ~ ^/cd(?:/|/dashboard)?$ { ... }

Computed on db-B-001, got 1 Gb using POWER(1024,3) but only 139 Mb using POWER(1024,2), so we're good with the default value there for now.

pillar/tower.sls already auto-loads dbserver/{{ minion_id }}.sls for every minion via salt-tower, so pillar/dbserver/ysul.sls alone is enough.

I see 3 blocks with the same 302 redirect.

Scope the diff to the T1130 commit only, the previous version wrongly included the unrelated T2289 (D4134) change from the same local branch.

COMFIRM

Document HTTP/HTTPS pitfall when pulling from the local Docker registry is closed

Document HTTP/HTTPS pitfall when pulling from the local Docker registry is complete

witch to callout primary, keep only the pull URL and a brief note that localhost:5000 no longer provides a certificate.

Instead of documenting the error in a warning block, I'd suggest we keep a primary callout block with directly the good instructions you wrote.

Works like a charm.