Skip to content

templates with parameter cannot be updated #2570

Closed

Description

@ammario
  1. Create a template with a parameter
  2. Try to update it
  3. See following error

Screen Shot 2022-06-21 at 11 42 52 PM

Activity

  1. ammario commented on Jun 22, 2022

    @ammario
    MemberAuthor

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

  2. sharkymark commented on Jun 22, 2022

    @sharkymark
    Contributor

    Yes I have experienced this as well.

  3. kylecarbs commented on Jun 22, 2022

    @kylecarbs
    Member

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

  4. ammario commented on Jun 22, 2022

    @ammario
    MemberAuthor

    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.

    asciicast

  5. kylecarbs commented on Jun 22, 2022

    @kylecarbs
    Member

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

  6. Emyrk commented on Jun 22, 2022

    @Emyrk
    Member

    @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.

  7. ammario commented on Jun 22, 2022

    @ammario
    MemberAuthor

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

  8. Emyrk commented on Jun 22, 2022

    @Emyrk
    Member

    @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.

  9. tjcran commented on Jun 22, 2022

    @tjcran

    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.

  10. misskniss commented on Jun 22, 2022

    @misskniss

    @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?

  11. added this to the Community MVP milestone on Jun 22, 2022
  12. Emyrk commented on Jun 22, 2022

    @Emyrk
    Member

    @misskniss #2463

    We can close this issue imo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

apiArea: HTTP API

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions