Prepare beta v1

[jerico]

This PR prepares for a v1 beta release.

The following tasks were covered:

• e779815 Renames altis command to altis-cli
• 4ebd605 d767c1a Codebase is up to date with latest/current versions of Node.js
  • Dependencies were updated to address critical warning about vulnerabilities
  • Features were tested using Nodejs v18 LTS
• 9196de5 altis-cli stack backup Fix to use correct API endpoint
• 2f070c6 altis-cli stack deploy
  • Updates region-related code that was deprecated
  • Adds prompt to ask which build to deploy
  • The prompt also effectively addresses ability to rollback deployed builds- Add pr
• ed7631f altis-cli stack scp
  • eb79ff6 Adds description and provided an example to proper use
  • Fixes local to remote upload was broken because the code checks for local existence of the remote destination. Fixed by pointing to the check to the local file.
• f876634 acae494 9d67f45 98805a2 altis-cli stack local-setup
  • Add feature to clone existing Altis codebase from the dashboard and automatically run composer install
• 9e0e77b Remove altis-cli stack sequel command
• ed7a72b Update copyright year

More information described here: #2

Looking for early feedback and marked this PR as ready for review.

[mikelittle]

This looks good. But I added a couple of questions

[mikelittle]

All looks good to me. Are there some docs on https://docs.altis-dxp.com/core/cli-command/ to update? (Probably needs a separate ticket.)

[rmccue]

Are there some docs on https://docs.altis-dxp.com/core/cli-command/ to update? (Probably needs a separate ticket.)

That's for the wp-cli commands available in the Core module, which is a different "product" in this sense; we have #3 for docs for altis-cli specifically

[kovshenin]

Changes look okay to me (as far as my JavaScript expertise goes) but I'm having trouble testing this. I'm running npm install and then:

altis-cli (prepare-beta-v1) ✗ $ bin/altis-cli  
Welcome to hm-cli!

[hm logo]

? Run initial setup? Yes
TypeError: configure is not a function
    at /Users/kovshenin/altis-cli/bin/altis-cli:92:12
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node version:

altis-cli (prepare-beta-v1) ✗ $ node -v
v18.13.0

Any pointers?

[jerico]

@kovshenin I missed updating the setup sequence. My understanding is we have the "setup" process to configure developer's ssh keys to access the sandbox servers before. This has been remove and there's nothing to configure. I need to update this to point to Vantage authentication flow instead.

To trigger Vantage authentication, you can any task such as ./bin/altis-cli stack list and it will offer to authenticate if no token has been found.

I'll fix the initial setup issue.

[jerico]

@kovshenin My bad. I had a change in altis-cli itself but missed pushing. It is fixed now.