Add support for replace package option

[starbelly]

hex_core and hex.pm have introduced an option to replace an existing package, this commit surfaces

• upgrade to hex 0.6.9

• add --replace switch on publish command

• Fix up publish options, previously there were strings where atoms were expected (element 0 of the option tuple)

• make --revert fully supported and useable

• add --package to support the --revert switch

• Start follow the command pattern laid out by the key command

• Improve description with supportive documentation

• move call to hex_api_release into rebar3_hex_client as publish/2

• update test suites were required

Output of rebar3 help for publish command

Publishes a new version of a package with options to revert and replace existing packages

Supported commmand combinations:

  rebar3 hex publish

  rebar3 hex publish --yes

  rebar3 hex publish --repo <repo>

  rebar3 hex publish --repo <repo> --yes

  rebar3 hex publish --revert <version> --package <package>

  rebar3 hex publish --revert <version> --package <package> --yes

  rebar3 hex publish --replace

  rebar3 hex publish --replace --yes

Argument descriptions:

  <repo>    - a valid repository, only required when multiple repositories are configured

  <version> - a valid version string, currently only utilized with --revert switch

  <package> - a valid package name, currently only utilized with --revert switch

Usage: rebar3 hex publish [-r <repo>] [-y [<yes>]] [--replace [<replace>]]
                          [-p <package>] [--revert <revert>]

  -r, --repo     Repository to use for this command.
  -y, --yes      Publishes the package without any confirmation prompts
                 [default: false]
  --replace      Allows overwriting an existing package version if it
                 exists. Private packages can always be overwritten,
                 publicpackages can only be overwritten within one hour
                 after they were initially published. [default: false]
  -p, --package  Specifies the package to use with the publish command,
                 currently only utilized in a revert operation
  --revert       Revert given version, if the last version is reverted the
                 package is removed

TODO:

• [x] Add tests for help on commands to ensure we do not crash
• [x] Add tests for --replace
• [x] Add tests for --revert

[starbelly]

One thing we could do here is support publishing a specific package since we've added a --package switch to support --revert as a switch. Thoughts?

[starbelly]

One thing we could do here is support publishing a specific package since we've added a --package switch to support --revert as a switch. Thoughts?

☝️ ignore this please. Will open another issue or set an agenda item for building & packaging to discuss this further.

[tsloughter]

@ferd you reviewed this?

@starbelly is it ready for merge?

I want to publish a release with my cut fix so figured it best to get all the PRs that are ready in first.

[starbelly]

@tsloughter Yeah, the only thing in question was the hacky way I'm silencing output in a test, but it's no solid reason to hold this up. Let me fix the conflict and merge.