You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
Activity
ammario commentedon Jun 22, 2022
I then tried recreating this template and hit the following error:

sharkymark commentedon Jun 22, 2022
Yes I have experienced this as well.
kylecarbs commentedon Jun 22, 2022
@ammario you are using a very old version of the CLI to update templates. This should have been fixed in: #2397. cc: @Emyrk
ammario commentedon Jun 22, 2022
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.
kylecarbs commentedon Jun 22, 2022
This is due to #2569. I'll publish a new release right now.
Emyrk commentedon Jun 22, 2022
@ammario old cli puts parameters at the
templatelevel. New cli puts them at theimport_joblevel. 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.
ammario commentedon Jun 22, 2022
Will this get automatically resolved by a fix or will I have to use a new template name?
Emyrk commentedon Jun 22, 2022
@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.
tjcran commentedon Jun 22, 2022
The original reported issue is now obsolete, correct? But we should open a new issue to investigate the error @Emyrk mentioned above
misskniss commentedon Jun 22, 2022
@Emyrk will you create an issue for this ☝️ if you have not already?
Emyrk commentedon Jun 22, 2022
@misskniss #2463
We can close this issue imo