Skip to content

Releases: PremiereGlobal/stim

v0.3.2: Merge pull request #72 from PremiereGlobal/badDefaultValues

06 Mar 20:57
bb724f6
Compare
Choose a tag to compare

v0.3.1

11 Feb 19:03
Compare
Choose a tag to compare

Improvements

  • changed thottle to 5 times and 2/4/8/16/32 sec

Bugfix

  • still fail if throttling happens more then 5 times

v0.3.0

11 Feb 07:53
Compare
Choose a tag to compare

Improvements

  • Allow vault to retry getting AWS creditials on throttle message: vault.retryOnThrottle:bool
  • Start work to commonize all configs to using more map style config based on stimpack name stimpack.key, IE vault.address kube.config.namespace

v0.2.1

21 Jan 19:12
Compare
Choose a tag to compare

Bugfix

  • Fixed defaulted value for prompt list.

v0.2.0

19 Jan 20:02
Compare
Choose a tag to compare

Improvements

  • Allow all config options to also be envVars using subpaths as _ which then get translated to - in viper config
  • Added filters for cluster and service account
  • Moved version to only output version nothing else. Removed unneeded else statement
  • Added semver requirement, and checking. Deploy added global.requiredVersion and global.minimumVersion to the stim.deploy.yaml, so you can enforce versions.
  • Adding validation to check for no arg for completion cmd
  • Tab completion functionality for bash and zsh

Bugfix

  • Fixed minor issue with logging Fatal, showing as Info
  • Fixed build/publish for versions
  • Upped version of kube-vault-deploy to fix checksum issue downloading kubectl >= 1.18
  • Hard set to alpine:3.11 since alpine:3.12 does not support py2 anymore

v0.1.7

18 May 21:43
4ebb760
Compare
Choose a tag to compare

Deprecations

  • For stim deploy, the HELM_VERSION environment variable for specifying Helm versions is now deprecated. Please use the .spec.tools.helm configuration for specifying the helm version to use. See deploy docs for more details.
  • For stim deploy, auto-detection of Helm v2 versions is now deprecated. Please use the .spec.tools.helm configuration for specifying the helm version to use. See deploy docs for more details.

Bugfix

  • Fixed a bug where running stim deploy via the default Docker method would not respect the spec.tools.helm version.

v0.1.6

11 May 06:23
c298207
Compare
Choose a tag to compare

Bugfix

  • Fixed bug in deploy config when setting variables in the global section did not propagate into subsections, like environments.

v0.1.5

28 Feb 19:58
8e8a82a
Compare
Choose a tag to compare

Bugfix

  • stim deploy - Fixed issue with cascading tool versions not working correctly. Certain instance tool versions would overwrite the tool version for other instances.
  • Changed displayed username in AWS web console for the STS federated login. The username was 'stim-user' and now matches the LDAP sAMAccountName short name.

v0.1.4

05 Feb 00:58
Compare
Choose a tag to compare

Improvements

  • Added new Docker image with the format premiereglobal/stim:v0.1.4-deploy. This container provides additional features for deployments with stim
    • Contains additional deploy utilities such as: bash, curl, zip, jq, less, python, git, yq, and aws
    • Entrypoint is bash to make it easier to run with custom commands
  • Updated Docker tagging
    • Master builds will now have the Docker tag master and master-deploy, with the stim version of stim/master
    • Tagged releases will continue having the tag scheme v0.1.4 and v0.1.4-deploy, but will also update the latest tags latest and latest-deploy. Doing stim version on any latest image will now reveal the actual version stim/vX.X.X, instead of stim/master.

v0.1.3

25 Jan 00:13
f520388
Compare
Choose a tag to compare

Improvements

  • Added --method to stim deploy allowing optional shell deployment. Will auto-select the best options if left empty.
    • shell deploy will be auto-selected if it detects that it is running in a container
  • Added configuration option for cache location. See docs/CONFIG.md

Bugfix

  • Fixed Pagerduty request to include all CLI parameters (for example source, component, etc.) as those were not actually being sent to Pagerduty previously