Provide some basic template variable expansion?

[arbourd]

Provide some basic template variable expansion?

[EugenMayer]

Thanks for coming back to this, but since i forked of, i did not want to invest here, someone lese should so it makes sense for you to put work into that.

I assume that it is the right call to let it where it is until someone else need it, which i entirely cannot understand i this should not be the case ( IMHO ). Thanks

[EugenMayer]

Considering that you have all the meta-data already in https://github.com/arbourd/concourse-slack-alert-resource/blob/master/concourse/build.go#L42 this seems to be an easy job. sure we jsut should use gotemplate for the template langauge {{}} but other then that, that might be close to a one liner

[arbourd]

When I first conceived this resource, I never really wanted (or considered) templating. It's a possibility but it's a large overhaul at the moment. I think one way this can be solved in the future is with #36 to allow custom messages to be set.

[EugenMayer]

Well setting the message by file and using template placeholders are not the same thing, but for sure expanding templates which are from files the same way would make sense.

So i would say that those are 2 entirely different features which may though be enriched by this, being it a normal string message or a file based one

[arbourd]

Maybe if we only exposed the BUILD variables that would be okay because they aren't available in tasks.

[arbourd]

@EugenMayer Where would you want these custom links anyways? They already exist in the footer.

[arbourd]

I'm assuming for the time being that you wanted this because of Mattermost, but the link does exist for Slack at the current time. I'm going to close this for now unless there is another reason why we might want those variables.