Wed, Jan 8
Thu, Jan 2
@kgaillot I don't think the existing XSLT error handler sets config warning, FYI. If we want that, we'll want a wishlist task for it, because it looks like it's gonna require some rearranging of cib_upgrade_err() that might be tricky to avoid redundant logs.
Dec 11 2024
Dec 5 2024
Since the risk of corner cases is so high, and our time for 3.0.0 is limited, I think the best approach would be to log a warning if a CIB contains ACLs with xpaths and the upgrade adds or renames any element or attribute. (We could possibly check whether an xpath exists that refers to an attribute, to reduce the scope a bit.) Something like: "WARNING: CIB syntax changes may invalidate ACLs that use 'xpath'. It is strongly recommended to run 'cibadmin --upgrade' then go through the updated CIB carefully to ensure ACLs still match the desired intent."
@kgaillot Can you weigh in when you have a chance? I know things are especially busy.
I figure it's unwise to work on the xpath case until we agree upon how we ought to address it -- if at all.
Dec 4 2024
CLPR#3747 fixes the case of ACLs that refer to dropped elements, but it doesn't do anything special for replaced elements yet.