Formula to install Datagrip on Windows, GNU/Linux and MacOS.
Table of Contents
See the full SaltStack Formulas installation and usage instructions.
If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.
If you want to use this formula, please pay attention to the FORMULA file and/or git tag,
which contains the currently released version. This formula is versioned according to Semantic Versioning.
See Formula Versioning Section for more details.
If you need (non-default) configuration, please pay attention to the pillar.example file and/or Special notes section.
Commit message formatting is significant!!
Please see How to contribute for more details.
None.
Meta-state (This is a state that includes other states).
This installs Datagrip package, manages Datagrip configuration file and then configures the development environment.
This state will install Datagrip from archive only.
This state will install Datagrip from source only.
This state will configure npmrc and/or environment and has a dependency on datagrip.install
via include list.
This state will install some Datagrip linux-alternatives on GNU/Linux.
Meta-state (This is a state that includes other states).
this state will undo everything performed in the datagrip meta-state in reverse order, i.e.
removes the configuration file and
then uninstalls the package.
This state will remove the configuration of Datagrip and has a
dependency on datagrip.package.clean via include list.
This state will remove Datagrip package and has a dependency on
datagrip.config.clean via include list.
This state will remove Datagrip package and has a dependency on
datagrip.config.clean via include list.
This state will remove Datagrip linux-alternatives on GNU/Linux.
Linux testing is done with kitchen-salt.
- Ruby
- Docker
$ gem install bundler
$ bundle install
$ bin/kitchen test [platform]Where [platform] is the platform name defined in kitchen.yml,
e.g. debian-9-2019-2-py3.
Creates the docker instance and runs the datagrip main state, ready for testing.
Runs the inspec tests on the actual instance.
Removes the docker instance.
Runs all of the stages above in one go: i.e. destroy + converge + verify + destroy.
Gives you SSH access to the instance for manual testing.