I then tried recreating this template and hit the following error:

Yes I have experienced this as well.

@ammario you are using a very old version of the CLI to update templates. This should have been fixed in: #2397. cc: @Emyrk

I updated an am hitting another ghost resource bug. I think some resources must've not been cleaned up when I was using the broken CLI.

This is due to #2569. I'll publish a new release right now.

@ammario old cli puts parameters at the template level. New cli puts them at the import_job level. So mixing can cause some interesting behavior.

But the new cli should prompt new params. New workspace params are not prompted at this time, but I am working on that.

Will this get automatically resolved by a fix or will I have to use a new template name?

@ammario actually I am unsure what that bug you are hitting is. I thought it was the pg constraint thing and trying to push a new param with the same scope name and id. Which would be fixed by the new cli because the scope id is now unique per version.

The error in the video I do not know what that is.

The original reported issue is now obsolete, correct? But we should open a new issue to investigate the error @Emyrk mentioned above

The error in the video I do not know what that is.

@ammario old cli puts parameters at the template level. New cli puts them at the import_job level. So mixing can cause some interesting behavior.

But the new cli should prompt new params. New workspace params are not prompted at this time, but I am working on that.

@Emyrk will you create an issue for this ☝️ if you have not already?

@misskniss #2463

We can close this issue imo