#aptible

Does .aptible.yml have an after_release directive to go along with before_release? Tried after_release and post_release without success…

hi mjacksonw, nope, only before_release is supported right now

what operations are you trying to run?

k, just making sure before I gave up – just post-release hooks to slack/etc, ideally after health tests have passed and images are actually being pushed live

ahh i see

sounds like another +1 for https://github.com/aptible/aptible-cli/issues/81

yup. i take it you'd want to configure that via .aptible.yml mjacksonw? or would it be the sort of thing where you'd have different configs for each environment (staging vs. production, etc.)

mjacksonw: i've been doing that at the application level: e.g. the application will post to slack when it starts up and performs self-checks

with different environments for dev/prod this has been pretty convenient

fancyremarker: yeah, I think .aptible.yml is fine, since we have our prod/staging status reflected in environment vars, which we can access at that stage

(at least for our purposes)

wayne: how do you avoid the duplicates from multiple instances of a particular service?

mjacksonw and wayne: how were/are you sending the hook to Slack? library or just a direct HTTP request?

just curl for us

fancyremarker: slack has go libs

cool. noted. we can roll that out via `after_release` pretty easily

i'll get on that, updating the priority

mjacksonw: event-based notifications only occur on a single app instance

so i guess this is a bit specific to me. also we only have one instance atm

:)

gotcha

startup_lyfe++

yup