-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding new addons should work automatically with other instances #163
Comments
Yeah, I don't think it does - see http://stackoverflow.com/a/38753156/452684 That said, could we add this as a post deploy task? Like running |
Or maybe we've reached the limit of what we can do using app.json, and we should switch to using the Heroku Platform API? |
@pezholio bothan-deploy does this now, right? |
Not yet, but it's unlikely Bothan is going to evolve any more to need any new addons anyway |
@pezholio could we close this ticket per your observation that current Bothan is not going to need any new addons - and withhold the question of whether its possible or not to some future subsequent iteration of bothan that necessitates its consideration? |
It's low priority for sure. |
PR #280 is wrangling with the same issues |
If my instance is auto-deploying from github, adding a new addon (i.e. pusher) should automatically happen. Not sure if Heroku supports this, but perhaps there is a configuration thing we can fix.
The text was updated successfully, but these errors were encountered: