You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on automating the creation of Heroku apps which use this deployment method (namely, with stack = container, no usage of buildpacks, there are no builds happening in Heroku side) and I'm evaluating what are the possibilities.
I'm currently considering forking this provider to adapt it to my needs and maybe contributing upstream if I arrive at something reusable.
I haven't found anything about this in older issues, so I'm opening this to start a discussion.
The text was updated successfully, but these errors were encountered:
Too bad, this would be really helpful to have! I tried using this provider with supported approach, which is heroku.yml and then Heroku builds the image for us -> but building such image is really slow, in my case it takes 7 minutes for something that on my machine gets built in a minute! So having an option to push Docker image would be amazing. I understand that it is not yet part of stable API, maybe it could also be marked as experimental/non-stable feature here in this provider?
This provider will not implement any resources using APIs that are not part of the Platform API. See previous comments by the maintainer(s) on this topic.
Hello!
Is there a plan to add support for Dockerized apps deployed with the Heroku Container Registry ?
I'm currently working on automating the creation of Heroku apps which use this deployment method (namely, with stack =
container
, no usage of buildpacks, there are no builds happening in Heroku side) and I'm evaluating what are the possibilities.I'm currently considering forking this provider to adapt it to my needs and maybe contributing upstream if I arrive at something reusable.
I haven't found anything about this in older issues, so I'm opening this to start a discussion.
The text was updated successfully, but these errors were encountered: