Skip to content

Releases: splicemachine/splicectl

v0.1.2

21 Jun 17:08
ff5104b

Choose a tag to compare

v0.1.2

Additions

Pull Request #7

  • added --cacert /path/to/cert.crt to pass in a certificate used as the CA to validate SSL connections
  • added support to read from SPLICECTL_CACERT=/path/to/cert.crt to auto-set the --cacert option.

Pull Request #6

  • Arch Linux package and updated build instructions

Pull Request #10

  • Added -a/--active and -p/--paused flags to the list database command.
    • If neither flag is used then all databases in their original order will be displayed.
    • If -a/--active is used then only active databases will be listed.
    • If -p/--paused is used then only paused databases will be listed.
    • If both are used then all databases will be listed with active databases listed first in a group and then all paused databases following them.

Pull Request #11

  • changelog command can now be used like so: splicectl changelog. It will display the markdown content of the changelog for the version of splicectl that you are using.

Pull Request #8

  • Added "op" as a valid option for cloud-provider.

Changes

Pull Request #12

Commands that use "database" in their subcommands now also accept "workspace" which is the preferred and documented option now. Both options work, but help messages will now show "workspace" in their examples and usage docs.
Commands that accept the flag "--database-name/-d" now also accept the flags "workspace" and "database". This functionality is not provided by cobra, so instead some additional logic was added that will determine which name to use in the event that more that one of the flags is supplied with a value. The final order of preferredness is: "--database-name/-d" > "workspace" > "database" where "--database-name/-d" is always used if provided and "database" is only used if no other name flag has been provided.
There was one command that should have used the "database" subcommand naming convention but instead used splice-database, namely the splicectl create splice-database. That old syntax is still aliased for backwards compatibility, but the naming conventions have now been brought in line with the other database related commands and now also supports syntax like:

  • splicectl create workspace
    and
  • splicectl create database
    No breaking changes have been implemented here, so all commands that used to work using the old names will still work.

Pull Request #9

--file input for the splicectl apply default-cr command is now partially validated before being sent to the splicectl/api.

v0.1.1

16 Mar 15:18
c1b15b8

Choose a tag to compare

v0.1.1

Additions

  • delete database functionality. (#4)
  • Get CloudManager accounts list. (#4)
  • pause database functionality
    • requires cloudmanager api endpoint pauseCluster. (#4)
  • resume database functionality
    • requires cloudmanager api endpoint resumeCluster. (#4)

Changes

  • create splice-database changed to call cloud manager
    • requires Cloud Manager API to support database/create call. (#4)
  • Moved the SemVer checking to each command function
    • outputs are also driven by the SemVer, output formatting started in v0.0.17 of the API. (#4)

Bug Fixes

  • removed debugging output. (#4)
  • list database will now prompt for database if not provided. (#4)

Special Attachments

  • splicectl_darwin and splicectl_linux are v0.1.1 with a --ca-cert /path/to/crt switch and SPLICECTL_CACERT=/path/to/crt environment variable to handle self-signed certs.

v0.1.0

16 Feb 10:54
b0e1183

Choose a tag to compare

v0.1.0

Additions

  • Initial move to separate repository. (#1)