All posts tagged with manifest


FY18 Q4 recap: Platform API for Partners & New Partner Portal GA

ecosystem , Director of Product & Partnerships

Need to quickly catch up on this past quarter's announcements? Here are the top three topics to tune in on:

The Platform API for Partners provides many official endpoints that allow you to introspect security settings, discover other customer instances of the same add-on, and much more. With the Platform API, add-ons have an OAuth client secret and a number of OAuth authorizations, one token per provisioned add-on; it is only used to authenticate requests to create the scoped tokens and not used to authenticate other requests to the Platform API.

Updated password requirements for the add-on manifest go into effect as of December 15, 2017. Add-on manifest password values are required...

FY18 Q3 recap: New Private Spaces Dublin Region Support & Heroku Webhooks GA

ecosystem , Director of Product & Partnerships

Need to quickly catch up on this past quarter's announcements? Here are the top three topics to tune in on:

Heroku has expanded regions availability for Private Spaces and introduced the general availability of the Dublin region on September 26, 2017. Heroku users are able to run apps in all of the following Private Spaces regions: Virginia, Oregon, Frankfurt, Tokyo, Sydney, and Dublin. Please verify that your add-on's manifest accurately reflect the supported Privates Spaces regions.

Heroku app webhooks for customers and add-on webhooks for partners are generally available. Partners are able to track many kinds of events relating to add-on resources on apps, domains, builds,...

FY18 Q2 recap: Heroku Continuous Integration GA & Ephemeral Apps

ecosystem , Director of Product & Partnerships

Need to quickly catch up on this past quarter's announcements? Here are the top three topics to tune in on:

Heroku announced the general availability of continuous integration (CI) on May 18, 2017. This new feature creates copies of staging apps to run tests, then destroys the app and its add-ons. With Heroku CI, you will see an increase in the number of default ephemeral plan resources regularly provisioned on Heroku review and CI apps. Previously, these apps used the add-on plan configured for staging.

As developers adopt CI/CD workflows, temporary deployments are becoming increasingly common. When ephemeral apps and their associated add-ons are destroyed, these actions should not...

Browse the blog archives or subscribe to the full-text feed.