Announcing the New Heroku Partner Portal for Add-ons

We are excited to announce that the new Heroku Partner Portal for Add-ons is now generally available.

The new portal offers an improved partner experience for building, managing, and updating Heroku add-ons. Our goal is to create a workflow that will give you more freedom and enable you to bring your add-ons to market more easily.

The new portal has been organized into a simple, elegant interface that is similar to the rest of Heroku's products. In each section, we've made more functionality available via the portal interface, where in the past emails or support tickets might have been necessary. This release brings a more visual approach as well as greater focus to creating and managing key aspects of your add-on offerings such as Marketplace Listing, Feature Plans, and Reports.

Partner Portal Screenshot

Marketplace Listing

The marketplace listing section of the portal is where you create or edit content for your add-on’s listing

Features and Plans Screen

Continue reading “Announcing the New Heroku Partner Portal for Add-ons”

Heroku Webhooks: Powering New Integrations and Real-time Notifications

We're happy to announce that Heroku app webhooks is now generally available for all Heroku customers.

App webhooks provide notifications when your Heroku app changes, including modifications to domain settings, releases, add-ons, and dyno formations. These notifications can empower your internal communications, dashboards, bots or anything else that can receive HTTP POST requests. Integrating with Heroku webhooks provides easy support for driving custom workflows and 3rd party tools.

Creating webhooks

With the webhooks CLI plugin, you can subscribe to events with a single command.

heroku plugins:install heroku-webhooks        
heroku webhooks:add -i api:release -l notify -u https://example.com/hooks -a your-app  

In this example, after a new release is created for your-app, Heroku sends a POST request to your server endpoint with the details of the event. The example below shows the first section of a typical POST request:

webhooks_blog2

Receiving webhooks

Webhooks are delivered by POST requests to a designated, publicly accessible URL.

Continue reading “Heroku Webhooks: Powering New Integrations and Real-time Notifications”

Announcing Platform API for Partners

Heroku has always made it easy for you to extend your apps with add-ons. Starting today, partners can access the Platform API to build a more secure and cohesive developer experience between add-ons and Heroku.

Advancing the Add-on User Experience

Several add-ons are already using the new Platform API for Partners. Adept Scale, a long-time add-on in our marketplace that provides automated scaling of Heroku dynos, has updated its integration to offer a stronger security stance, with properly scoped access to each app it is added to. Existing customer integrations have been updated as of Friday May 12th. All new installs of Adept Scale will use the more secure, scoped Platform API.

Opbeat, a performance monitoring service for Node.js developers, is using the Platform API in production to sync their user roles to match Heroku. It is also synchronizing metadata, so that its data stays in sync

Continue reading “Announcing Platform API for Partners”

Announcing the New Heroku CLI: Performance and Readability Enhancements

Today we are announcing the newest version of the Heroku CLI. We know how much time you spend in the CLI as developers and how much pride you take in being able to get things done quickly. Our new CLI has big improvements in performance as well as enhanced readability for humans and machines.

Tuned for Performance

CLI response time is made up of two parts: the API response time and the performance of the CLI itself, and the latter is where we’ve made big improvements. While a typical Unix user should experience responses that are around half a second faster, the biggest gains are for Windows users, as the new CLI no longer has a Ruby wrapper.

When we measured the time it takes for the info command in the old vs. new CLI, it decreases from 1690 to 1210 in Unix, and 3409 to 944 milliseconds in Windows!

Performance_windows
heroku_regions_old
heroku_regions_new
heroku_regions_grep
heroku_regions_jq
heroku_dashboard

Continue reading “Announcing the New Heroku CLI: Performance and Readability Enhancements”

Sunsetting Heroku’s Legacy Platform API (v2)

Two years ago we released the Heroku Platform API (v3), providing a supported way to automate and instrument Heroku and making it even easier for you to build new products. Today we are deprecating the legacy, unofficial version of the API that preceded it (v2), as its usage is limited and we are focusing development on the newer, officially-supported API.

We will sunset v2 of the API on April 15, 2017. For security reasons, we will be sunsetting support of auth in query string sooner, which we will announce in the Changelog.

If you are using the older version of the API, we recommend transitioning to v3 as soon as possible. Please reach out to us through support if you have any questions as you make the transition.

Sunsetting Heroku’s Legacy Platform API (v2)

Two years ago we released the Heroku Platform API (v3), providing a supported way to automate and instrument Heroku and making it even easier for you to build new products. Today we are deprecating the legacy, unofficial version of the API that preceded it (v2), as its usage is limited and we are focusing development on the newer, officially-supported API.

We will sunset v2 of the API on April 15, 2017. For security reasons, we will be sunsetting support of auth in query string sooner, which we will announce in the Changelog.

If you are using the older version of the API, we recommend transitioning to v3 as soon as possible. Please reach out to us through support if you have any questions as you make the transition.

Introducing Add-on Controls: Standardize Add-ons for Your Team

Today we are introducing Add-on Controls for Heroku Enterprise customers. This new feature enables team leads to whitelist specific add-ons for approved use within their organization, choosing from our marketplace of over 150 add-on services. The ability to standardize the add-on technologies being used across all the apps and developers in their organization is something many customers have asked for, especially those with fast-growing teams.

Standardizing Add-ons Using the Whitelist

To get started with Add-on Controls, the first step is for the team lead, or anyone who has admin permissions, to build the Add-ons Whitelist. There is a new section on the organization’s settings page, where this whitelist can be created and then the Add-on Controls can be enabled. Don’t worry; enabling the whitelist does not break any existing add-ons, but simply prevents add-ons that are not on the whitelist from being installed going forward.

Addons-Controls-Dashboard

Managing Whitelist Exceptions

In the

Addons-Controls-Exceptions
Addons-Controls-Elements
Addons-Controls-Restricted

Continue reading “Introducing Add-on Controls: Standardize Add-ons for Your Team”