As you suspected, the startup of application is failing (JPA validation failures) due to missing column.
Although we are using Spring Data JPA, but since we have our own table schemas to manage as well, we are maintaining a separate (liquibase based) mechanism for managing database schema upgrades.
As you pointed out, we are planning to make the required column addition and removal. The only thing we are wondering, what would be the impact of removing public_key column.
I will try to search for documentation on semantic meaning and usage of newly inserted columns. (cloud_id and authentication)
We are not currently in process of migrating the application to Forge. So did not dig too deep into posts and articles related to Connect to Forge migration. Is that something that is going to become a requirement in near future ? Are Connect apps being completely phased out ?
Hi @SumeetSingh , the cloud_id and authentication are for Connect-on-Forge apps only and they are for allowing apps to authenticate using OAuth 2.0. There is no documentation for that at this point except the code comment, we will schedule this work of adding more documentations around this.