![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
hubot-heroku
Advanced tools
A hubot library that exposes heroku commands via Heroku's Platform API, with focus of letting non privileged developers carry out tasks around deployments, but not run dangerous commands or get access to the data.
Under Heroku's permission model, giving someone access to push/promote to production means giving full access to the data as well. This is generally not a good practice and for certain companies, it might be non-compliant.
Our team wanted to let every engineer do deployments without giving production access. We started this by using atmos/hubot-deploy and atmos/heaven, but that didn't the ability to run migrations, set config variables etc. hubot-heroku was made with this consideration in mind.
By the way, I'm also actively looking for co-contributors!
Deployment usually involves some form of CI process. Hence it is best suited for a robust solution like Github deployments, where you can set required CI contexts etc.
This robot is focused on letting you run auxiliary commands around the heroku system, so developers don't have to be given production access to independently manage deployments.
You can set config variables using this. Hence the Heroku API key used should not have access to your hubot instance on Heroku. For example:
hubot heroku config:set my-hubot HUBOT_ADMIN=dr_evil
# Muhaha, now I'm to use hubot's other commands to take over the world
npm install hubot-heroku --save
hubot-heroku
to external-scripts.json
(e.g. ["hubot-heroku", "some-other-plugin"]
)HUBOT_HEROKU_API_KEY
to a heroku account's API key. This user must have access to the apps you want to use this script on.hubot help
. The commands usually follow hubot heroku The API key can be obtained here.
Use hubot help
to look for the commands. They are all prefixed by heroku. (e.g. hubot heroku restart my-app
)
Some commands (hubot help will be a better source of truth):
hubot heroku info <app>
- Returns useful information about the apphubot heroku dynos <app>
- Lists all dynos and their statushubot heroku releases <app>
- Latest 10 releaseshubot heroku rollback <app>
- Rollback to a releasehubot heroku restart <app> <dyno>
- Restarts the specified app or dyno/s (e.g. worker
or web.2
)hubot heroku migrate <app>
- Runs migrations. Remember to restart the app =)hubot heroku config <app>
- Get config keys for the app. Values not given for securityhubot heroku config:set <app> <KEY=value>
- Set KEY to value. Case sensitive and overrides present keyhubot heroku config:unset <app> <KEY>
- Unsets KEY, does not throw error if key is not presentFor example, hubot heroku config:set API_KEY=12345
If you get hubot errors, this might help:
Reference the API documentation for more information. Search for "Error Responses".
Run tests by running npm test
npm install -g node-inspector
node-inspector --no-preload --web-port 8123
# In your hubot folder
npm link /path/to/hubot-heroku
coffee --nodejs --debug node_modules/.bin/hubot
Visit http://127.0.0.1:8123/debug?port=5858
and use debugger
statements to pause execution.
PRs and Issues greatly welcomed. Please read Contributing for more information.
FAQs
Run heroku commands via hubot without direct access to Heroku
The npm package hubot-heroku receives a total of 0 weekly downloads. As such, hubot-heroku popularity was classified as not popular.
We found that hubot-heroku demonstrated a not healthy version release cadence and project activity because the last version was released 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
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.