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 https://github.com/meshcloud/collie-cli/issues/143
• collie version now shows installed and detected cli's, closing https://github.com/meshcloud/collie-cli/issues/131. The new process runner system also verifies cli installation status lazily, significantly improving collie invocations times
• the new command structure solves previous issues https://github.com/meshcloud/collie-cli/issues/129 https://github.com/meshcloud/collie-cli/issues/96
• Azure platforms are now filtering tenants on an AAD Tenant level, which is equivalent to the root-management group, closing https://github.com/meshcloud/collie-cli/issues/31

New Contributors

• @dritz01234 made their first contribution in https://github.com/meshcloud/collie-cli/pull/141

Full Changelog: https://github.com/meshcloud/collie-cli/compare/v0.9.0...v0.10.0