DEV2 Clone Impact on Redwood VB Studio Customizations (P2T Refresh)

Summary:

Hi Team,

We are looking forward to knowing the impact when we do refreshing/cloning non-prod environments with P2T

We are planning to clone the DEV2 environment from PRODUCTION (P2T) for the post Go-Live support, but we made all the Redwood Customizations/Personalization’s through VB Studio in DEV2 environment and now when DEV2 is getting cloned from PRODUCTION (P2T) then we need to know if there is any impact on DEV2 existing VB Studio Project and respective repositories/extensions which contains all our Redwood Customizations/Personalization’s. The point here is, we made DEV2 as a source system for all VB Studio changes and migrating to UAT or PROD (DEV2 > UAT, DEV2 > PROD) respectively. Can you please check and advise on