Using repetitive blocks for slack_config in alertmanager config file

How we can omit having repetitive blocks for similar slack_configs. Is there a chance defining just -channel and define all other fields in only one place within alertmanager config file...?

These are my receivers:

receivers:
  - name: 'slack-admin'
    slack_configs:
    - channel: '#slack-admin'
      send_resolved: true
      icon_url: https://avatars3.githubusercontent.com/u/3380462
      title: '{{ template "slack.slack_alert.title" .}}'
      text: '{{ template "slack.slack_alert.text" .}}'

  - name: 'slack-ch1'
    slack_configs:
    - channel: '#slack-ch1'
      send_resolved: true
      icon_url: https://avatars3.githubusercontent.com/u/3380462  
      title: '{{ template "slack.slack_alert.title" .}}'
      text: '{{ template "slack.slack_alert.text" .}}'

I'd like if I can define them something like this:

  - name: 'slack-admin'
    slack_configs: '{{ template slack.slack_config admin }}'
  - name: 'slack-ch1'
    slack_configs: '{{ template slack.slack_config ch1 }}'

and define other fields in template files like we do for title & text for example.

The issue names no implementation files or tests. Start by locating receiver slack_configs parsing and the existing title/text template handling; determine how reusable Slack configuration templates would fit there. Done means similar receivers can share the non-channel fields while retaining distinct channels, with coverage for the requested configuration form.