v0.14.1

What's Changed

• edit the contributing document by @ishabakeh in #179
• Feature/predefined landing zones by @j0g3sc in #181

Includes new KitBundle functionality to setup LZs lightning fast.
For now contains only one KitBundle for Azure Enterprise Scale LZ.

v0.13.0

What's Changed

• feat: support running collie commands from subdirectories of repo by @JohannesRudolph in #176
• Feature/windows support fixes by @JohannesRudolph in #177
• Feature/deno cliffy upgrade by @JohannesRudolph in #175

Full Changelog: v0.12.0...v0.13.0

v0.12.0

What's Changed

• Feature/missing double quotation by @ishabakeh in #167
• Feature/consistent deploy approve behavior by @JohannesRudolph in #169
• fix: generate a kit readme in collie init by @JohannesRudolph in #170
• feat: collie init ensures an initialized git repo by @JohannesRudolph in #171

New Contributors

• @ishabakeh made their first contribution in #167

Full Changelog: v0.11.0...v0.12.0

v0.11.0

What's Changed

• Feature/tenant tree command by @JohannesRudolph in #158
• Feature/optimize docs folder by @JohannesRudolph in #159
• fix: infinite recursion when current directory is not a collie reposi… by @JohannesRudolph in #161
• fix: date serialization issue in tenant cost command json output by @JohannesRudolph in #164
• Feature/deploy raw option by @JohannesRudolph in #162
• Feature/platform module template by @JohannesRudolph in #163

Full Changelog: v0.10.0...v0.11.0

v0.10.0

What's Changed

Welcome to the next iteration of collie! Whereas collie was a great tool to help cloud shepherds run their clouds before, collie will now also help you build them.

One consistent theme of feedback we got about collie from professional cloud shepherds like enterprise architects and platform engineers is that their key challenge lies in building and operating landing zones for their cloud customers. With its unified model to list tenants, tags, costs and IAM across all major cloud platforms, collie has been a great help to shepherds already running a flock of clouds. However, building up landing zones involves a myriad of different tools and technologies, as well as a complex landscape of functional requirements from your customers as well as compliance requirements from security stakeholders.

Staying true to the spirit of building a convenient operator experience on top of established CLI tools (like aws, az, gcloud), collie now also offers utilities to build and deploy modular landing zones leveraging a GitOps approach on top of terraform and terragrunt. Our vision is that collie will empower cloud shepherds to build and operate their own Landing Zone Construction Kit as a means to rapidly assemble compliant landing zones across different clouds.

This change in scope of course means that we are introducing a number of breaking changes in this release. Experienced collie users should however have no problem finding all the existing capabilities under the collie tenant command. Here's an overview of the new command structure:

  Commands:

    init          - initialize a new collie repository in the current directory                     
    foundation    - Create, list and deploy cloud foundations covering all your cloud platforms     
    tenant        - List tenants in your cloud foundations and manage tags, cost and IAM            
    kit           - Manage a kit of reusable modules to build landing zones in your cloud foundation
    compliance    - Manage compliance frameworks and audit their implementation in your cloud foundation                                                                      
    interactive   - Experimental interactive mode to explore your cloud foundations    

The most important change is that collie now assumes you're working from a git repository ("collie repository") to manage one or more foundations. A foundation manages a set of cloud platforms (e.g. an AWS Organization, an AAD Tenant or a GCP Organization) as an intuitive tree of configuration files in your repository. This allows cloud shepherds to easily switch between e.g. a dev and prod environment, while building their landing zones from a common set of IaC modules. We will provide updated documentation and tutorials for this new approach together with our Landing Zone Construction Kit soon.

This release addresses a number of existing issues, all of which I propose to close with this PR

• collie now uses a new process runner subsystem with consistent logging and observability capabilities, closing #143
• collie version now shows installed and detected cli's, closing #131. The new process runner system also verifies cli installation status lazily, significantly improving collie invocations times
• the new command structure solves previous issues #129 #96
• Azure platforms are now filtering tenants on an AAD Tenant level, which is equivalent to the root-management group, closing #31

New Contributors

• @dritz01234 made their first contribution in #141

Full Changelog: v0.9.0...v0.10.0

v0.9.1

Release v0.9.1

v0.8.0

Bump version to v0.8.0

v0.7.0

feat: bump version to 0.7.0 (#114)

v0.6.0

feat: Update version to 0.6.0 (#99)

v0.5.0

Feature/release 0.5.0 (#95)

* feat: Add tutorial links directly in README. (#52)

* feat: Add tutorial links directly in README.

* And removed GitOps section, which is not supported yet.

* Update README.md

* Update README.md

Added a different caption

* feat: Avoid cli setup checks when not required (#68)

* feat: Avoid cli setup checks when not required

In order to optimize startup time, especially when only issuing a non
cloud-cli required command, collie now only checks cloud cli configuration
when required.

* fix: setup logger before running commands and await it

not awaiting the logger configuration can cause loosing logs

* feat: run cli checks concurrently

see discussion in https://github.com/meshcloud/collie-cli/pull/68

* feat: add debug logs to ShellRunner for every command

* style: deno fmt

Co-authored-by: Johannes Rudolph <[email protected]>

* Feature/issue 56 (#71)

* feat: detect installed cli versions match expectations

if not, give installation hints via collie readme.

fixes #56

* fix: handle GCP projects with empty IAM policies (#80)

fixes #67

* fix: use azure subscription id instead of name to prevent word-splitting (#79)

fixes #76

* Feature/cache statistics (#78)

* refactor: generate entries summary generically for all platforms

* feat: add query statistics to tty table output

This lets users know whether results are served from cache or
if they're queried from the cloud. At the moment only "tenant list"
command supports this.

Fixes #72

* feat: add query statistics to all tenant commands

Fixes #72

* refactor: extract QueryStatistics class into its own module

* test: add a tests for query statistics

* feat: slightly tweak the query stats message.

* feat: correctly print cache and cloud query statistics for hybrid query

hybrid queries can occur when e.g. running
- collie tenant list -> partially fills the tenant cache
- collie tenant iam -> uses tenants from cache, adds IAM info

* refactor: Uses OOP patterns

Simplifies the statistics decorator to be less intrusive.

Co-authored-by: Thomas Felix <[email protected]>

* Update issue templates

* Update issue templates

* fix: Spinner animation overwrites error message (#85)

Improves the spinner animation termination to avoid part of the error message
writing into the spinner animation text.

* feat: Tags are shown in table cost view (#90)

* fix: Fix costs / IAM missing in cached tenants. (#91)

* Feature/add windows support (#87)

* feat: add windows support for collie

* feat: add windows binary to releases

* fix: differentiation in posix and win32 path

* fix: Replaces var with let

* Fixed issue found while testing Windows

* Added global `isWindows` var for consistency

Co-authored-by: Thomas Felix <[email protected]>
Co-authored-by: Jelle den Burger <[email protected]>

* Bump version to 0.5.0

Co-authored-by: Thomas Felix <[email protected]>
Co-authored-by: Johannes Rudolph <[email protected]>
Co-authored-by: Thomas Felix <[email protected]>
Co-authored-by: Dennis Murtic <[email protected]>