{"action":"opened","issue":{"url":"https://api.github.com/repos/concourse/concourse/issues/1439","repository_url":"https://api.github.com/repos/concourse/concourse","labels_url":"https://api.github.com/repos/concourse/concourse/issues/1439/labels{/name}","comments_url":"https://api.github.com/repos/concourse/concourse/issues/1439/comments","events_url":"https://api.github.com/repos/concourse/concourse/issues/1439/events","html_url":"https://github.com/concourse/concourse/issues/1439","id":247446574,"number":1439,"title":"`validate-pipeline` works on pipelines with `((parameter))` templating","user":{"login":"astrieanna","id":1205394,"avatar_url":"https://avatars3.githubusercontent.com/u/1205394?v=4","gravatar_id":"","url":"https://api.github.com/users/astrieanna","html_url":"https://github.com/astrieanna","followers_url":"https://api.github.com/users/astrieanna/followers","following_url":"https://api.github.com/users/astrieanna/following{/other_user}","gists_url":"https://api.github.com/users/astrieanna/gists{/gist_id}","starred_url":"https://api.github.com/users/astrieanna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/astrieanna/subscriptions","organizations_url":"https://api.github.com/users/astrieanna/orgs","repos_url":"https://api.github.com/users/astrieanna/repos","events_url":"https://api.github.com/users/astrieanna/events{/privacy}","received_events_url":"https://api.github.com/users/astrieanna/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-08-02T16:20:24Z","updated_at":"2017-08-02T16:20:24Z","closed_at":null,"body":"# Feature Request\r\n\r\n## What challenge are you facing?\r\n\r\nOur pipelines are heavily templated to maintain support for multiple versions in productions. We've (very happily) taken advantage of the new `((parameters))` that allow complex (arrays, nested structures) as values.\r\n\r\nPreviously, we used `validate-pipeline` as a way to check our yaml syntax before setting the pipeline. We like to do as much testing as possible before possibly breaking our team's ci. Now, `validate-pipeline` doesn't work for us because it doesn't handle template variables.\r\n\r\n## A Modest Proposal\r\n\r\nWe'd be happy to go back to being able to use `validate-pipeline`. Since we do want to check as much as possible locally, being able to pass `--load-vars-from` to `validate-pipeline` would work well for us because it could template in the actual values and ensure they are the right type.\r\n\r\n"}}
{"actor":{"display_login":"astrieanna"}}