Variables with the following scopes are not currently supported: Machine
Team
- [x] I've assigned a team label to this issue
Severity
Several customers affected, workaround does not reach expectations
Version
Present in 2021.1
Latest Version
I could reproduce the problem in the latest build
What happened?
A project cannot be exported if there is one machine scoped variable.
Reproduction
- Set up a deployment target.
- Create a project.
- Go to Variables, Project, add a new variable.
- Set the scope of the variable to the deployment target from step 1.
- Export the project.
Error and Stacktrace
The items you are exporting are not currently supported: Variables with the following scopes are not currently supported: Machine. Found variables named my-proj-variable443. Reference path: Project 'my-proj437' => Project Variables
More Information
Affected customers:
- https://help.octopus.com/t/project-export-library-variable-set-issue/26930
- [Internal] https://octopus.zendesk.com/agent/tickets/85401
- [Internal] https://octopusdeploy.slack.com/archives/C01HZFJRYSH/p1660175107817279
- [Internal] https://octopus.zendesk.com/agent/tickets/82785
- [Internal] https://octopus.zendesk.com/agent/tickets/82734
More info: https://octopus.com/blog/exporting-projects
Workaround
Remove the machine scoped variable, export the project and add the variable back again.
Another affected customer (enterprise): https://octopus.zendesk.com/agent/tickets/144287
Affected another customer: https://octopus.zendesk.com/agent/tickets/152902
- also appears to be affecting the project export process (tenants associated w/ project do not get exported)
- my thoughts are that it doesn't make it that far in the process
Another affected user [internal link]: https://octopus.zendesk.com/agent/tickets/155490
Another affected user [internal link]: https://octopus.zendesk.com/agent/tickets/170816
Another affected user [internal link]: https://octopus.zendesk.com/agent/tickets/179273