fix(crossplane-azure): Refactoring

[srishtih]

No description provided.

[octo-sts]

⚙️ Build Failed: Configuration

stat /home/build/cmd/provider/family: directory not found

Build Details

Category	Details
Build System	go/build
Failure Point	go build command attempting to build from ./cmd/provider/family directory

Root Cause Analysis 🔍

The build process is trying to build a Go binary from the path './cmd/provider/family' but this directory does not exist in the source code. This indicates a mismatch between the expected project structure and the actual source code layout for the crossplane-provider-family-azure subpackage.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• splunk-otel-collector/0.139.2 package update #71924

Suggested Changes

File: crossplane-provider-azure.yaml

• modification (data.packages.items)
  Original:

family: 'provider-family-azure'
authorization: 'provider-azure-authorization'
managedidentity: 'provider-azure-managedidentity'
sql: 'provider-azure-sql'
storage: 'provider-azure-storage'

Replacement:

authorization: 'provider-azure-authorization'
managedidentity: 'provider-azure-managedidentity'
sql: 'provider-azure-sql'
storage: 'provider-azure-storage'

Content:

Remove the 'family' entry from the packages data items since the ./cmd/provider/family directory does not exist in the source code

Click to expand fix analysis

Analysis

The similar fix shows that when a Go build fails due to a missing directory (./cmd/migratecheckpoint), the solution was to remove the entire subpackage that was trying to build from that non-existent path. In the splunk-otel-collector case, they removed the migratecheckpoint subpackage and its companion compat package because the source directory didn't exist in the updated version. This pattern suggests that when upstream removes or restructures directories, the corresponding subpackages should also be removed.

Click to expand fix explanation

Explanation

The fix removes the 'family' entry from the packages data structure because the corresponding source directory './cmd/provider/family' does not exist in the crossplane-contrib/provider-upjet-azure repository at version v2.3.0. This follows the same pattern as the similar fix where a missing directory caused a build failure, and the solution was to remove the reference to that non-existent path. The subpackages are generated dynamically from the data.packages.items, so removing the family entry will prevent the build system from attempting to build from the non-existent directory. The other providers (authorization, managedidentity, sql, storage) should remain as they likely have corresponding directories in the source code.

Click to expand alternative approaches

Alternative Approaches

• Verify the actual directory structure in the source repository and update the path if the family provider was moved to a different location
• Check if the family provider was split into multiple providers or merged with another provider in this version
• Update to a different version of the package where the family provider directory exists if this functionality is required

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.