Terraform Provider: SDKv2 Organization Refactor

Hey guys, let's dive into a crucial update for our Terraform provider: the SDKv2 Organization refactor, which aligns perfectly with SDK issue #104. This isn't just a minor tweak; it's about making our management of Organizations and Virtual Data Centers (VDCs) cleaner, more consistent, and much more user-friendly. We're focusing strictly on the Organization and VDC aspects, ditching any unrelated resources.* keys from our outputs, and making sure our selectors and filters are crystal clear, just like we did with the VDC (#1183) changes. This effort ensures that when you're defining and managing your cloud infrastructure, it's intuitive and follows best practices.

Aligning Organization Management with SDK v2

So, what's the big picture here? We're talking about making the cloudavenue_organization resource and any related data sources in our Terraform provider line up perfectly with the latest version of our Go SDK (v2), specifically addressing issue #104. The main goal is to streamline how you interact with Organization and Virtual Data Center (VDC) configurations. We're deliberately cutting out any extraneous information from our Get and Update outputs – specifically, anything that looks like resources.*. This keeps the output focused on what's essential for managing your organizations. Furthermore, we're going to harmonize the way we use selectors versus filters. You know how we clarified that for VDCs in issue #1183? We're applying that same level of clarity and consistency here. This means less confusion and a more predictable experience when you're querying or modifying your cloud environments. Think of it as tidying up the house so everything is in its right place and easy to find.

Current Provider State: A Blank Slate for Organization

Before we jump into the refactoring, it's important to note where we're starting from regarding the Organization surface in the provider codebase. A quick audit revealed that there isn't currently an Organization resource or data source implemented in the provider repository. A search for relevant code returned no matches, which might seem a bit surprising. However, this actually presents a fantastic opportunity! We have an umbrella issue, #1160, tracking the broader migration of Organization management to SDK v2. This means that this specific issue allows us to introduce the Organization surface aligned with SDK v2 right from the get-go. Instead of refactoring existing, potentially inconsistent code, we're building it fresh, ensuring it adheres to the v2 SDK standards and our newly defined best practices from day one. This clean slate approach minimizes the risk of carrying over old issues and allows us to implement a more robust and maintainable solution from the start. It's like building a new room in your house – you can design it exactly how you want it, incorporating all the latest features and making sure it flows perfectly with the rest of your home.

Impacts: Enhancing the Organization Surface

Let's break down the specific impacts this refactor will have on how you interact with the cloudavenue_organization resource and its related functionalities. These changes are designed to make your life easier and your configurations more robust.

1. Overview: Focusing on the Core

The overview section of our documentation and output is getting a much-needed trim. We're keeping it laser-focused on the essential aspects of Organization and VDC management. This means you'll no longer see references to