Provides the ability to list Heroku apps that can be accessed by your account, to retrieve detailed information about each app, database version, and other information, and to store this as JSON.
It is primarily intended to be used for creating maintenance plans for Stack and others.
Install the gem and add to the application's Gemfile by executing:
$ bundle add heroku-app-info
If bundler is not being used to manage dependencies, install the gem by executing:
$ gem install heroku-app-info
And, at the moment it depends on the Heroku CLI.
The Heroku CLI | Heroku Dev Center
$ heroku-app-info -h
After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/wtnabe/heroku-app-info.
FAQs
Unknown package
We found that heroku-app-info demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.