At GameStop we are leveraging a custom solution/pipeline to handle code migration and deployment from one environment to another. We are using Metadata List snap to list projects, accounts, pipelines, tasks from source project then using Metadata Create snap to recreate them in target environment (by specifying org/projectspace/project information). This solution seems to be working fine for all asset types: Account, Pipeline, Task. However it is failing for asset type PROJECT where I am always getting the same error: Error creating asset /GameStop/projects/TargetProject, Reason: Absolute path required when I try to create a any new project.
Did anyone stumble upon that error before: Absolute path required ?? I know that I am using the right absolute path correctly because it is working fine for other asset type: Account, Task, Pipelines. So why I cannot use it to create target project?
The leading / (forward slash) is needed because it has to be an absolute path. I tried to remove it but I got an error complaining about invalid asset_type because it has to be a Dir: Failure: Invalid asset_type, expected “Dir”, Reason: Invalid asset_type, expected “Dir”
Any particular reason you have the expression toggle selected?
For me, the following path works for creating a new project:
I have the expression toggle selected because I am using a quotation in between because at runtime real use case I have using arguments combined with text. But it doesn’t matter I am still getting that error regardless when I remove it below
