Feature/upgrade fabrica

[alexlovelltroy]

Description

This pull request introduces significant improvements to the project’s structure, developer workflow, and documentation to better align with the Fabrica framework and modernize the codebase. The changes include the addition of new configuration files, Makefile enhancements for code generation, updates to documentation and developer instructions, improved support for authentication in the CLI, and a refactor of the server’s WireGuard integration.

Key changes:

Fabrica Integration & Configuration

• Added .fabrica.yaml and apis.yaml to define project metadata, enabled features, and resource groups/types for Fabrica-based code generation. [1] [2]
• Updated Makefile to add generate and generate-check targets for Fabrica code generation, supporting both released and local Fabrica builds. [1] [2]
• Updated all generated Go files to reference the new code generation workflow and copyright year. [1] [2] [3] [4] [5] [6] [7]

Documentation & Developer Experience

• Updated documentation (README.md, .github/copilot-instructions.md, CLOUDINIT.md) to reflect new resource locations (apis/cloud-init.openchami.io/v1/), code generation steps, and WireGuard integration patterns. [1] [2] [3] [4] [5] [6] [7]
• Clarified and centralized instructions for adding new resources, running tests, and regenerating code using Fabrica. [1] [2]

CLI Improvements

• Added support for a JWT bearer token via the --token flag and CLOUD_INIT_TOKEN environment variable in the CLI, enabling future authentication support. [1] [2] [3] [4]

Server Refactoring

• Refactored server initialization to move WireGuard integration into a single function (registerCustomServerIntegrations), improving maintainability and modularity. [1] [2] [3]
• Updated references to generated code and removed direct dependencies on the old resource paths. [1] [2]

Miscellaneous

• Improved Makefile clean target to also clear Go build cache.
• Updated comments and instructions in generated files to match new workflow. [1] [2] [3] [4] [5] [6] [7] [8]

These changes modernize the project, streamline developer workflows, and set the foundation for future enhancements, especially around code generation and authentication support.

Checklist

• My code follows the style guidelines of this project
• I have added/updated comments where needed
• I have added tests that prove my fix is effective or my feature works
• I have run make test (or equivalent) locally and all tests pass
• DCO Sign-off: All commits are signed off (git commit -s) with my real name and email
• REUSE Compliance:
  • Each new/modified source file has SPDX copyright and license headers
  • Any non-commentable files include a <filename>.license sidecar
  • All referenced licenses are present in the LICENSES/ directory

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

---

For more info, see Contributing Guidelines.

[travisbcotton]

As far as I can tell this is good to go.