Consider a postfunction plugin that defines both functions and access fields.
"functions" was the old way. "access" is the new way.
While converting, deck changes function -> access and thus overwrites over the original access function.
This is unintentional and leads to invalid conversions where customers miss out on the custom functions they wrote. Thus, before converting deck should check for the pre-existing access field and then perform the conversions.
Refer schemas and docs to understand how 2.8 dealt with both access and functions present together.
Refer: https://kongstrong.slack.com/archives/C04349E4KRC/p1773153822687389
Consider a postfunction plugin that defines both
functionsandaccessfields."functions" was the old way. "access" is the new way.
While converting, deck changes
function->accessand thus overwrites over the original access function.This is unintentional and leads to invalid conversions where customers miss out on the custom functions they wrote. Thus, before converting deck should check for the pre-existing access field and then perform the conversions.
Refer schemas and docs to understand how 2.8 dealt with both access and functions present together.
Refer: https://kongstrong.slack.com/archives/C04349E4KRC/p1773153822687389