Skip to content

Release News

Jump to bottom
Jeff Felchner edited this page Dec 30, 2020 · 9 revisions

Starting with 2.11.0 I'll be adding human-readable release notes in addition to the CHANGELOG.

3.0.0-rc1 - December 30th, 2020

See Chamber 3.0 Upgrade Notes for a lengthy discussion.

  • Remove Hashie As A Dependency
  • Remove Ability To Access Settings Via Object Notation
  • Remove Ability To Use Predicate Syntax (eg Chamber.env.key_name?)
  • Remove Ability To Use Symbolized Keys With Bracket Syntax (eg Chamber.env[:key_name])
  • Added dig! As A Replacement For Most Removed Syntax Cases

2.14.1 - December 30th, 2020

  • Added dig! As A Replacement For Syntax That Will Be Removed In 3.0
  • Added Deprecation Warnings For Syntax That Will Be Removed In 3.0

2.14.0 - December 29th, 2020

2.13.0 - May 30th, 2019

2.12.4 - May 29th, 2019

  • Change .gitignore lookup to recurse directories in case Chamber is not being invoked from the root of the project - #64
  • Ignore dots and dashes in the hostname when detecting the keyfiles associated with those namespaces - #56
  • Fix namespaces not being resolved correctly when dealing with namespaced keys - #58

2.12.3 - January 27th, 2018

  • Add better error messages when environment variables are unable to be converted to the type specified in the YAML file. - #57

2.12.2 - January 24th, 2018

  • Internal bugfix involving how options were passed in from the CLI that could cause them to not be respected.

2.12.1 - January 15th, 2018

  • Relax Thor's dependency requirement - @jrmhaig - #55

2.12.0 - January 15th, 2018

  • Added official Sinatra and Padrino integrations.
  • Added chamber sign to allow users to sign their application settings with a special key and allow any developer to verify those settings without the special key. Full documentation is here.
  • Added ability to parse ISO8601 formatted environment variables and have them be converted into Ruby Time objects. See Coercions.

2.11.0 - January 12th, 2018

  • Namespaced Key Pairs were added which allow users to specify more than one level of access to their settings.
  • chamber init learned how to create keys for multiple namespaces.
  • Environment variables can now be coerced from multiple different types based on the type that was declared in the YAML file.

Kompanee Logo Copyright ©2023

  1. Release News
  2. Gem Comparison
  3. 12-Factor App Rebuttal
  4. Environment Variable Problems
    1. Lack of Complex Values
    2. Organization
    3. Environment Sharing
    4. Team Member Syncing
    5. Environment Syncing
    6. Local Settings
    7. Tracking Changes
  5. Installation
    1. Initialization
    2. In a Ruby Project
    3. In a Rails Project
    4. In a Rails Engine
    5. In a Sinatra Project
    6. In a Padrino Project
    7. In a Hanami Project
  6. Basics
    1. File Layout
    2. Defining Settings
    3. Accessing Settings
    4. Namespace Basics
      1. Inline Namespaces
      2. Host-Based Settings
    5. Encryption Basics
      1. Encrypting Your Settings
      2. Accessing Encrypted Settings
    6. Environment Variables
  7. Defining Settings
    1. ERB Preprocessing
    2. Runtime Values
    3. Dynamic Templating
  8. Accessing Settings
    1. Dig
  9. Verifying Settings
  10. Namespaces
    1. File-Based Namespaces
    2. Mix and Match
    3. Custom Namespaces
  11. Environment Variables
    1. Coercions
  12. Integrations
    1. Git Commit Hooks
    2. Cloud Services
  13. Encryption
    1. Keypair Encryption
    2. What Keys Can Do
    3. Encrypting Nested Structures
    4. Namespaced Key Pairs
    5. Re-Securing
    6. Loading Keys from ENV
  14. Advanced Usage
    1. Manually Specifying Settings Files
    2. Outputting Your Settings
    3. Specifying Multiple Namespaces
    4. Handling Duplicates/Collisions
    5. Extending Chamber
  15. Command Line Reference
    1. init
    2. show
    3. files
    4. sign
    5. secure
    6. unsecure
    7. compare
Clone this wiki locally