The problem with machine scoping is that we have no way of ensuring that the deployment target will exist wherever the project is imported and that it is driven by the machine-id. This could result in broken variables, data inconsistency and even variables being scoped to the wrong deployment targets.
So, even if we carried those variables across to a new Space or Instance, you’d still have to go through each variable and fix the machine scoping and any that you miss could result in a major issue for a deployment.
Due to this, the safest option is to exclude them entirely.
The only way to include them would be to also include deployment targets which isn’t something that is within scope for this feature.
So from what you are saying, we would have to start all of our projects again from scratch ? We have over 300 tenants each with their own numerous project variables and I don’t really look forward to this task.
Could we have the ability to include the deployment targets and resolve them manually ? At the moment I don’t see a way of moving to the cloud.
This was meant to be me trialling the use of the cloud. If I remove all of the machine scoping then the projects would no longer work for our server version.
Would it be possible to add a feature request to exclude machine scoped variables from the export ?
I have passed this along to the team working on this feature. It is only the first iteration, so, hopefully this is something that can be improved upon.
I feel that excluding these variables and then generating a report at the end detailing which variables were excluded and from where would give users the ability to still migrate and rectify the missing items in the simplest way possible.