"the tide abides for, tarrieth for no man, stays no man, tide nor time tarrieth no man"
Yes, you should migrate from V2 to V3 today unless...
The Slack integration we all use and love for V2 is not compatible with V3. And although a V3 version exists, it is not currently working.
We recommend the CLI as an alternative for telling HOPS what to do (build, deploy, etc), and the CLI and Web Interface as an alternative to keeping track of what is happening.
If you still prefer to use Slack, sit tight until we've built the Slack integration. (And also let us know that you're waiting, please.)
- Maybe you have command line scripts refering to the V2 CLI
- Maybe you have internal documentation refering to the V2 CLI/web/slack bot
- Maybe you have a big team, and coordinating a change like this requires a little planning
The V3 CLI exists as a subcommand on the V2 CLI. If you're keeping your tools updated, you might already have the V3 CLI on your computer!
- Install HOPS CLI, see how to install cli!
hops self-updateto make sure you have the latest and greatest
- Confirm that all is well by running
hops v3 versionand observe that the version is
hops_cli/v0.2.0or greater. Great!
We have to log in to V3.
hops v3 loginwhere you'll be directed to the new web interface, where you'll be asked to login with your GitHub account.
- After you've logged, go to https://www.headless-operations.no/tokens and generate a new token.
- Paste the token into the terminal.
- Confirm that you have access to apps by running
hops v3 list-apps. If you don't see any apps listed, ask for help in
You are now able to use V3!
To get your app on to V3, you first need1 to get it off V2.
#iterapp-logs, on the Iterate Slack, write
/iterapp deregister APPNAME where
APPNAME obviously is the name of the app you intend to deregister.
Note that this does not undeploy or remove your app from the internet. It only turns off the build/deploy automation from V2.
You can probably, technically have the app registered in both V2 and V3, but messages from the system might make less sense, you might get a lot of weird noise and the HOPS Team does not support nor condone dual registration.
In your terminal, write
hops v3 register --cluster iterapp iterate/APPNAME where
APPNAME obviously is the name of your app. If the GitHub repository is not under the
iterate organization, replace
iterate with the correct organization.
The world is your oyster, run
hops v3 for a list of exciting opportunities! Visit https://headless-operations.no to witness the endless percolation of builds, deploys, logs.
#hops-support and tell us how to improve this migration guide.
hops v3 unregisterto learn how to deregister from V3.
/iterapp register iterate/APPNAMEwhere
APPNAMEobviously is the name of the app you want to reregister.