Maintain Your Heroku Architect Certification for Summer '22
Learning Objectives
After completing this unit, you'll be able to:
- Enable Multi-Factor Authentication (MFA) for Enterprise accounts.
- Manage the runtime handling of $HOME directory.
- Validate fields in the app.json are the correct type.
- Enable the Heroku-22 stack.
- Upgrade to PostgreSQL 14.
Salesforce Certification
If you hold the Salesforce Heroku Architect credential, keep in mind that you need to complete this module by the due date to maintain your certification. Another important part of maintaining your credential is ensuring your Trailhead and Webassessor accounts are linked.
Interested in learning more about getting certified? Check out the Salesforce Certified Heroku Architect credential.
Salesforce introduced a ton of great feature enhancements over the past year. Let's take a look at some of the more important ones.
Note: While anyone can earn this badge, this module is designed for those who hold the Salesforce Heroku Architect certification.
Enterprise Accounts Can Now Require MFA
What's new?
Enterprise Accounts can now require Multi-Factor Authentication (MFA) for all account members.
How does it work?
Enterprise Account users with manage privilege can enable this setting in the Login Security section on the Settings tab of your Enterprise Account.
Changes to Common Runtime Handling of $HOME Directory When Running Container Images
What's new?
The Common Runtime environment variable will no longer be overwritten, which will bring the Common Runtime container support in line with Private Spaces and with other container runtimes.
Why was this added?
Previously the Common Runtime would overwrite the $HOME env var with the value / when running container images.
How does it work?
If your Heroku app has come to rely on the previous behavior, you can set a config var to get the previous behavior.
heroku config:set HOME=/
app.json Validation Has Been Added
What's new?
Field validation is enforced around app.json for use on the Heroku platform.
How does it work?
The fields in the app.json are now required to be of the correct type. For example, the addons key must be of type Array and the environments values must be of type Object.
In addition, the only valid environments key names are “test” and “review”.
For more information, see our page on app.json Schema.
Heroku-22 Stack Is Now Generally Available
What's new?
Heroku-22, our stack based on Ubuntu 22.04 Long Term Support, is now generally available. It will be supported until the end of April 2027.
How does it work?
If your organization uses Review Apps or Heroku CI, you should test Heroku-22 by defining your stack in app.json.
{
"stack": "heroku-22"
}
Existing apps can be upgraded by running this command and pushing a new build.
heroku stack:set heroku-22
The Heroku-22 stack article contains a list of changes over the Heroku-20 stack. Instructions for upgrading and testing a new stack with your app also contain information specific to Heroku-22.
PostgreSQL 14 Is Now the Default for All Database Plans
What's new?
Previously, PostgreSQL 14 was the default version on Hobby Postgres plans. PostgreSQL 14 is now the default for all plans (hobby, standard, premium, private, and shield).
How does it work?
All pg:upgrade commands upgrade databases to version 14. Developers are encouraged to upgrade.
More technical info for PostgreSQL:
- Heroku Postgres Plans
- PostgreSQL project's release notes for version 14
- PostgreSQL version support on Heroku
Resources
- Heroku Dev Center: Enterprise Accounts can now require MFA
- Heroku Dev Center: Changes to Common Runtime handling of $HOME directory when running container images
- Heroku Dev Center: app.json validation has been added
- Heroku Dev Center: Heroku-22 stack is now generally available
- Heroku Dev Center: PostgreSQL 14 is now the default for all database plans
