spinifex

module
v1.13.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Jul 21, 2026 License: AGPL-3.0

README

Go License Docs

What is Spinifex? · Platform · Deploy · AWS services · Components · Architecture · Installation · Docs


Spinifex: the open, AWS-compatible cloud you run yourself

Spinifex, built by Mulga, recreates the AWS services your software already uses (EC2, EBS, S3, VPC, IAM) on infrastructure you control. Move workloads off the hyperscalers, run AI at a fraction of the cost, or take the cloud to the edge, without rewriting a line. The exact build you ship to AWS, Spinifex serves on your own hardware: same APIs, same Terraform, same SDKs.

What is Spinifex?

Spinifex is an open-source infrastructure platform that recreates the AWS service surface (EC2, EBS, S3, VPC, IAM) on bare-metal, edge, and on-premises environments. Run cloud-native software without a hyperscaler.

Most AWS alternatives wrap an API and call it a cloud. We rebuilt the engineering underneath: distributed object storage with erasure coding, block storage built to survive failure, and compute on bare metal. That depth is the reason your software runs unchanged, instead of rewritten.

It's built for teams that need:

  • The AWS tooling they already use (AWS CLI, SDKs, Terraform), with nothing to rewrite
  • Full control of the stack: your hardware, your network, your data, your keys
  • A cloud that keeps running offline, through disconnection, with no external control plane
  • An open core (AGPL-3.0), auditable and yours to keep, with no lock-in

You change where your software runs, not what it is.

The Platform

From commodity hardware up to unmodified AWS tooling, every layer is replaceable and yours to own.

Three ways to deploy

One AWS-compatible surface, three deployment shapes. Pick the one that matches your reality; the platform on top is the same.

Neocloud

Lift and shift onto a partner Neocloud. Move workloads off the hyperscalers and onto our Neocloud partner ecosystem without rewriting them. GPU capacity (H100 / H200 / B200), cheaper, available now. Change an endpoint, keep the software.

On-premise

Bring your own hardware and host Spinifex in your own data centre. A real multi-node HA cluster integrated with your storage and networking, with full control of stack, data, and jurisdiction. A predictable bill, no egress surprises, an auditable open-source core.

Edge

Cloud where the cloud can't reach. Air-gapped sites, vehicles, vessels, factories, and clinics. Compute next to the data, running through disconnection, on hardware you own. The same AWS APIs your software already uses.

AWS compatibility

Speak the AWS API surface, natively. The AWS SDKs, AWS CLI, and Terraform: everything you deploy on AWS deploys on Spinifex unchanged. At the edge, on-premise, or on a partner Neocloud.

Service What it is Status
EC2 Compute Available
EBS Block storage Available
S3 Object storage Available
VPC Networking Available
IAM Identity & auth Available
ALB / NLB Load balancers Available
EKS Kubernetes Available
ECR Container registry Available
ECS Container service Available
RDS Databases Q3 2026

Roadmap items (Q3 2026) ship under the same AWS API surface. Code written for AWS today keeps working the moment they land. Track what's shipped in the release notes.

Core Components

Spinifex (Compute Service – EC2 Alternative)

Spinifex is a minimal VM orchestration layer built on top of QEMU, exposing APIs similar to EC2. It manages lifecycle operations like start, stop, and terminate, using QEMU's QMP interface. Designed to be straightforward and scriptable, Spinifex lets you launch VMs using the AWS CLI, SDKs, or Terraform—without needing Kubernetes or heavyweight orchestrators. Keep in mind, you can also setup a Kubernetes environment using Spinifex with underlying instances.

  • EC2-like VM management on bare metal
  • Launches with cloud-init metadata support
  • Works with standard AWS tooling
Viperblock (Block Storage – EBS Alternative)

Viperblock is a high-performance, WAL-backed block storage service that replicates volumes across multiple nodes. It's built for reliability and speed, with support for snapshots, recovery, and direct connection to QEMU instances using NBD or virtio-blk.

  • Fast, durable virtual disks
  • Replication for resilience
  • Exposed over NBD or embedded in VMs
  • Supports high performance WAL logs using local NVMe drives to reduce IO traffic to S3.
  • In memory read/write block cache for blazing performance.
Predastore (Object Storage – S3-Compatible)

Predastore is a fully S3-compatible object storage system. It supports the AWS S3 API, including Signature V4 authentication, multipart uploads, and Terraform provisioning. Data is chunked and distributed across nodes using Reed-Solomon erasure coding, making it fault-tolerant and ideal for large-scale or low-bandwidth scenarios.

  • S3-compatible API and auth
  • Multipart uploads, streaming reads/writes
  • Data redundancy with Reed-Solomon encoding

Architecture at a Glance

Every AWS API call is authenticated at the gateway, published to a NATS subject, and answered by whichever daemon claims it. Daemons are stateless: scale horizontally by starting more. No etcd, no Kubernetes, no external control plane. Just systemd units, a NATS cluster, and your hardware. Deep dive: docs/DESIGN.md.

Key Features

  • AWS-compatible APIs. Use the AWS CLI, SDKs, and Terraform you already know. Repoint your endpoint and ship; nothing to rewrite.
  • Zero cloud dependency. Runs entirely on your hardware. No phone-home, no control plane, no external authority. Works fully offline.
  • Bare-metal compute. QEMU-based with direct hardware access. No hypervisor tax, no abstraction overhead.
  • Built-in storage. Block and object storage included: NVMe caching, Reed-Solomon erasure coding, and replication out of the box.
  • Edge-first architecture. Designed for disconnected, contested, and resource-constrained environments from day one.
  • Open core, no lock-in. AGPL-3.0 with a commercial option. Inspect it, modify it, deploy it. The platform is yours to keep.

Installation

Installation requires an Ubuntu / Debian system. See the detailed documentation at docs.mulgadc.com for maintaining and installing Spinifex.

Bare Metal ISO

The recommended installation is a bootable x86 installer for bare-metal hardware.

curl -fLO https://iso.mulgadc.com/spinifex.iso

Follow the USB install guide to write the ISO to USB and install on your hardware. The install guide walks through the full process.

Single Node Install

The installation is straightforward to set up and running on a single node for testing purposes. Debian 13 is currently supported, additional Linux distributions are on the immediate roadmap.

Prerequisite: Linux bridge for networking.

Spinifex requires a Linux bridge configured on the host for VM networking. See the single-node install guide prerequisites for setup details.

curl -fsSL https://install.mulgadc.com | bash

sudo /usr/local/share/spinifex/setup-ovn.sh --management

sudo spx admin init --node node1 --nodes 1

sudo systemctl start spinifex.target

export AWS_PROFILE=spinifex

aws ec2 describe-instance-types
Development Setup

For a complete development environment see the Source Install documentation

Component Repositories

Spinifex coordinates these independent components:

Each component can be developed independently. See component-specific documentation for focused development guides.

Spinifex UI

Spinifex ships with a built-in web console — an optional alternative to the AWS CLI, SDKs, and Terraform. If you're familiar with the AWS Management Console, the Spinifex UI fills the same role: a browser-based view of your instances, volumes, buckets, VPCs, and IAM resources, without leaving your own network.

The console is served by each node on port 3000 over TLS, and becomes available as soon as spinifex.target is up:

open https://YOUR_NODE_IP:3000
  • Same API, different surface. Every action in the UI is the same AWS SigV4 call the CLI makes — so RBAC, audit trails, and IAM policies apply uniformly.
  • Single sign-on against your AWS credentials. Log in with the access keys from ~/.aws/credentials on the node where Spinifex is installed — no separate user database.
  • Self-hosted, works offline. The UI is embedded in the Spinifex binary and served from the node itself. No external CDN, no analytics calls, no cloud dependency.

For the full walkthrough — first-time TLS certificate trust, login, and feature tour — see Launching the Web UI in the cluster setup guide.

Development Philosophy

Built by Engineers, For Engineers

Spinifex is developed by experienced infrastructure engineers with deep AWS expertise, including former AWS team members who understand the intricacies of building production-grade cloud services. Our team brings decades of combined experience from AWS, enterprise infrastructure, and edge computing environments.

Real-World Experience:

  • Production AWS service development and operations
  • Large-scale infrastructure deployment and management
  • Edge computing and resource-constrained environments
  • Enterprise security and compliance requirements
AI-Assisted Development

While Spinifex is architected and implemented by experienced engineers, we leverage Claude Code (Anthropic's AI coding assistant) to accelerate certain development tasks. This approach combines human expertise with AI efficiency:

How We Use Claude Code:

  • Code Generation: Boilerplate AWS API structures and handlers
  • Documentation: Comprehensive development guides and API documentation
  • Testing: Test case generation and validation scenarios
  • Refactoring: Large-scale code restructuring and optimization

What Remains Human-Driven:

  • Architecture Decisions: Core system design and scalability choices
  • Security Implementation: Authentication, encryption, and threat modeling
  • Performance Optimization: Real-world performance tuning and benchmarking
  • Production Operations: Deployment strategies and operational procedures

This hybrid approach ensures Spinifex benefits from both proven engineering expertise and modern development acceleration, while maintaining the quality and reliability standards required for production infrastructure.

Trademarks

"AWS", "Amazon Web Services", and all related service names (EC2, EBS, S3, VPC, IAM, and others) are trademarks of Amazon.com, Inc. or its affiliates. Mulga Defense Corporation and Spinifex are independent and not affiliated with, endorsed by, or sponsored by Amazon.com, Inc. or Amazon Web Services, Inc. References to AWS services describe interoperability and compatibility only.

License

Spinifex is open source under the GNU Affero General Public License v3.0. You're free to use, modify, and deploy it anywhere you need reliable infrastructure without depending on centralized cloud platforms.

Directories

Path Synopsis
cmd
dhcptest command
dhcptest is a diagnostic tool that runs a DHCP DORA handshake using the same nclient4 library and options that spinifex-vpcd uses for gateway pool leases.
dhcptest is a diagnostic tool that runs a DHCP DORA handshake using the same nclient4 library and options that spinifex-vpcd uses for gateway pool leases.
ecr-credential-provider command
ecr-credential-provider is a kubelet exec credential provider that lets a Spinifex EKS worker node pull images from the internal Spinifex ECR registry.
ecr-credential-provider is a kubelet exec credential provider that lets a Spinifex EKS worker node pull images from the internal Spinifex ECR registry.
ecs-agent command
ecs-agent runs inside a Spinifex ECS container instance (a guest VM booted from the ECS-AMI, with containerd baked in).
ecs-agent runs inside a Spinifex ECS container instance (a guest VM booted from the ECS-AMI, with containerd baked in).
ecs-agent/credentials
Package credentials supplies AWS SigV4 credentials to the ecs-agent.
Package credentials supplies AWS SigV4 credentials to the ecs-agent.
ecs-agent/runtime
Package runtime is the ecs-agent's container-runtime seam.
Package runtime is the ecs-agent's container-runtime seam.
eks-gateway-fetch command
eks-gateway-fetch runs inside the EKS K3s control-plane VM and fetches a control-plane resource from the host through the AWS gateway, instead of dialing core NATS directly.
eks-gateway-fetch runs inside the EKS K3s control-plane VM and fetches a control-plane resource from the host through the AWS gateway, instead of dialing core NATS directly.
eks-gateway-publish command
eks-gateway-publish runs inside the EKS K3s control-plane VM and relays a single publication to the host through the AWS gateway, instead of dialing core NATS directly.
eks-gateway-publish runs inside the EKS K3s control-plane VM and relays a single publication to the host through the AWS gateway, instead of dialing core NATS directly.
eks-konnectivity-cert command
Command eks-konnectivity-cert mints, then reuses, an ECDSA-P256 serving certificate for the on-node konnectivity-server, signed by the K3s cluster CA.
Command eks-konnectivity-cert mints, then reuses, an ECDSA-P256 serving certificate for the on-node konnectivity-server, signed by the K3s cluster CA.
eks-token-webhook command
eks-token-webhook is the K8s TokenReview webhook authenticator baked into the eks-server AMI.
eks-token-webhook is the K8s TokenReview webhook authenticator baked into the eks-server AMI.
eks-webhook-cert command
Command eks-webhook-cert mints, then reuses, a self-signed ECDSA-P256 serving certificate for an in-cluster admission webhook and prints its base64 PEM so the addon renderer can embed it as the webhook Secret + each caBundle.
Command eks-webhook-cert mints, then reuses, a self-signed ECDSA-P256 serving certificate for an in-cluster admission webhook and prints its base64 PEM so the addon renderer can embed it as the webhook Secret + each caBundle.
installer command
installer/autoinstall
Package autoinstall reads headless install parameters from environment variables exported by spinifex-init.sh from the kernel cmdline.
Package autoinstall reads headless install parameters from environment variables exported by spinifex-init.sh from the kernel cmdline.
installer/branding
Package branding centralises Mulga/Spinifex visual identity constants used by the installer TUI.
Package branding centralises Mulga/Spinifex visual identity constants used by the installer TUI.
installer/firstboot
Package firstboot writes the oneshot systemd service and configuration that completes Spinifex provisioning on the first real boot after installation.
Package firstboot writes the oneshot systemd service and configuration that completes Spinifex provisioning on the first real boot after installation.
installer/install
Package install performs the disk installation steps after the UI has collected configuration.
Package install performs the disk installation steps after the UI has collected configuration.
installer/systemd
Package systemd writes systemd unit files and drop-ins into an installed system root during the Spinifex ISO installation process.
Package systemd writes systemd unit files and drop-ins into an installed system root during the Spinifex ISO installation process.
installer/ui
Package ui presents the interactive installer TUI using bubbletea and lipgloss.
Package ui presents the interactive installer TUI using bubbletea and lipgloss.
lb-agent command
lb-agent runs inside load balancer VMs and manages HAProxy configuration.
lb-agent runs inside load balancer VMs and manages HAProxy configuration.
spinifex command
internal
ecrauth
Package ecrauth mints ECR registry credentials by SigV4-signing GetAuthorizationToken against the Spinifex AWS gateway's ECR endpoint and decoding the returned AWS:<jwt> token into Basic-auth parts.
Package ecrauth mints ECR registry credentials by SigV4-signing GetAuthorizationToken against the Spinifex AWS gateway's ECR endpoint and decoding the returned AWS:<jwt> token into Basic-auth parts.
ecsgw
Package ecsgw is the on-VM SigV4 client the ecs-agent uses to reach the AWS gateway over HTTPS instead of connecting to NATS directly.
Package ecsgw is the on-VM SigV4 client the ecs-agent uses to reach the AWS gateway over HTTPS instead of connecting to NATS directly.
eksgw
Package eksgw is the on-VM SigV4 client used by EKS helpers (eks-gateway-publish, eks-token-webhook) to POST over HTTPS to the AWS gateway instead of NATS.
Package eksgw is the on-VM SigV4 client used by EKS helpers (eks-gateway-publish, eks-token-webhook) to POST over HTTPS to the AWS gateway instead of NATS.
fipsboot
Package fipsboot enforces FIPS 140-3 at startup via blank import in every binary.
Package fipsboot enforces FIPS 140-3 at startup via blank import in every binary.
gwsign
Package gwsign SigV4-signs on-VM requests to the AWS gateway.
Package gwsign SigV4-signs on-VM requests to the AWS gateway.
imdscreds
Package imdscreds fetches AWS instance-role credentials from the in-guest IMDS endpoint (169.254.169.254) using IMDSv2.
Package imdscreds fetches AWS instance-role credentials from the in-guest IMDS endpoint (169.254.169.254) using IMDSv2.
stsauth
Package stsauth mints task-role credentials by SigV4-signing sts:AssumeRole against the Spinifex AWS gateway.
Package stsauth mints task-role credentials by SigV4-signing sts:AssumeRole against the Spinifex AWS gateway.
tlsconfig
Package tlsconfig pins the cluster-wide TLS 1.3 curve preference list.
Package tlsconfig pins the cluster-wide TLS 1.3 curve preference list.
spinifex
gateway
Package gateway provides the AWS-compatible API gateway for the Spinifex platform.
Package gateway provides the AWS-compatible API gateway for the Spinifex platform.
gateway/acm
Package gateway_acm is the HTTP-side glue between awsgw and the ACM handlers.
Package gateway_acm is the HTTP-side glue between awsgw and the ACM handlers.
gateway/bedrock
Package gateway_bedrock is the HTTP-side glue between awsgw and the Ochre (bedrock / bedrock-runtime) handlers.
Package gateway_bedrock is the HTTP-side glue between awsgw and the Ochre (bedrock / bedrock-runtime) handlers.
gateway/ec2/spotinstance
Package gateway_ec2_spotinstance provides the gateway-side orchestration for AWS-compatible Spot Instance Requests.
Package gateway_ec2_spotinstance provides the gateway-side orchestration for AWS-compatible Spot Instance Requests.
gateway/ecr
Package gateway_ecr is the HTTP-side glue for the OCI Distribution Spec v2 registry surface (/v2/*) served by awsgw.
Package gateway_ecr is the HTTP-side glue for the OCI Distribution Spec v2 registry surface (/v2/*) served by awsgw.
gateway/ecrapi
Package gateway_ecrapi is the HTTP-side glue for the ECR control plane: the AWS JSON 1.1 surface dispatched by X-Amz-Target (AmazonEC2ContainerRegistry_V20150921.<Action>), matching aws-sdk-go's service/ecr request shape.
Package gateway_ecrapi is the HTTP-side glue for the ECR control plane: the AWS JSON 1.1 surface dispatched by X-Amz-Target (AmazonEC2ContainerRegistry_V20150921.<Action>), matching aws-sdk-go's service/ecr request shape.
gateway/ecrauth
Package gateway_ecrauth implements the ECR auth bridge: it mints and verifies the self-contained ES256 JWT that GetAuthorizationToken issues and the /v2/* registry surface accepts (Authorization: Bearer | Basic AWS:<jwt>).
Package gateway_ecrauth implements the ECR auth bridge: it mints and verifies the self-contained ES256 JWT that GetAuthorizationToken issues and the /v2/* registry surface accepts (Authorization: Bearer | Basic AWS:<jwt>).
gateway/ecs
Package gateway_ecs is the HTTP-side glue for the ECS control plane: the AWS JSON 1.1 surface dispatched by X-Amz-Target (AmazonEC2ContainerServiceV20141113.<Action>), matching aws-sdk-go's service/ecs request shape.
Package gateway_ecs is the HTTP-side glue for the ECS control plane: the AWS JSON 1.1 surface dispatched by X-Amz-Target (AmazonEC2ContainerServiceV20141113.<Action>), matching aws-sdk-go's service/ecs request shape.
gateway/eks
Package gateway_eks is the HTTP-side glue between awsgw and the EKS handlers.
Package gateway_eks is the HTTP-side glue between awsgw and the EKS handlers.
gateway/spx
Package spx implements spinifex platform-level gateway handlers (version, node status, VM inventory) that are distinct from the AWS-compatible APIs.
Package spx implements spinifex platform-level gateway handlers (version, node status, VM inventory) that are distinct from the AWS-compatible APIs.
gateway/tagging
Package gateway_tagging is the HTTP-side glue between awsgw and the Resource Groups Tagging API.
Package gateway_tagging is the HTTP-side glue between awsgw and the Resource Groups Tagging API.
gpu
handlers/dns
Package dns is the control-plane DNS record writer.
Package dns is the control-plane DNS record writer.
handlers/ecr
Package ecr holds the ECR registry handlers and the predastore storage layout that backs them.
Package ecr holds the ECR registry handlers and the predastore storage layout that backs them.
handlers/ecs/bus
Package bus defines the Layer-2 internal scheduler↔agent NATS subjects and wire payloads for the ECS control plane (ecs-v1.md Q14).
Package bus defines the Layer-2 internal scheduler↔agent NATS subjects and wire payloads for the ECS control plane (ecs-v1.md Q14).
handlers/eks
Package handlers_eks implements the EKS control-plane API surface for Spinifex.
Package handlers_eks implements the EKS control-plane API surface for Spinifex.
handlers/quota
Package handlers_quota enforces per-account service quotas in the AWS gateway.
Package handlers_quota enforces per-account service quotas in the AWS gateway.
handlers/sysinstance
Package sysinstance holds the boot-agnostic contract for system-managed VMs.
Package sysinstance holds the boot-agnostic contract for system-managed VMs.
lbagent
Package lbagent implements the LB config agent that runs inside load balancer VMs.
Package lbagent implements the LB config agent that runs inside load balancer VMs.
nbd
network/external
Package external is L5 of the spinifex network stack: VPC-facing external connectivity (IGW, EIP, NAT Gateway).
Package external is L5 of the spinifex network stack: VPC-facing external connectivity (IGW, EIP, NAT Gateway).
network/external/dhcp
Package dhcp provides an in-process DHCPv4 client (spinifex-vpcd) for single-attempt DORA/RENEW/RELEASE with KV-persisted leases.
Package dhcp provides an in-process DHCPv4 client (spinifex-vpcd) for single-attempt DORA/RENEW/RELEASE with KV-persisted leases.
network/host
Package host is L0 of the spinifex network stack: OVS bridges (br-int, br-ext), uplink port, and external CIDR.
Package host is L0 of the spinifex network stack: OVS bridges (br-int, br-ext), uplink port, and external CIDR.
network/invariants
Package invariants holds executable tests that pin the spinifex network layer tree to the safety and liveness invariants declared in ADR-0006 (docs/development/proposals/az-local-architecture/0006-spinifex-network-layer-contract.md).
Package invariants holds executable tests that pin the spinifex network layer tree to the safety and liveness invariants declared in ADR-0006 (docs/development/proposals/az-local-architecture/0006-spinifex-network-layer-contract.md).
network/ovn
Package ovn is L1 of the spinifex network stack: the OVN Northbound DB client interface and implementations.
Package ovn is L1 of the spinifex network stack: the OVN Northbound DB client interface and implementations.
network/ovn/mock
Package mock provides an in-memory implementation of ovn.Client for tests.
Package mock provides an in-memory implementation of ovn.Client for tests.
network/ovn/nbdb
Package nbdb contains libovsdb model structs for the OVN Northbound tables used by Spinifex VPC networking.
Package nbdb contains libovsdb model structs for the OVN Northbound tables used by Spinifex VPC networking.
network/ovn/ovntest
Package ovntest boots an in-process OVN Northbound database for tests.
Package ovntest boots an in-process OVN Northbound database for tests.
network/policy
Package policy (L3) attaches data-plane policy — ACLs, NAT, routes — to L2 logical objects.
Package policy (L3) attaches data-plane policy — ACLs, NAT, routes — to L2 logical objects.
network/reconcile
Package reconcile is the network stack's intent-actual reconciliation layer.
Package reconcile is the network stack's intent-actual reconciliation layer.
network/subscribers
Package subscribers translates VPC lifecycle NATS events into calls against the network/{topology,policy,external} managers.
Package subscribers translates VPC lifecycle NATS events into calls against the network/{topology,policy,external} managers.
network/topology
Package topology is L2 of the spinifex network stack.
Package topology is L2 of the spinifex network stack.
objectstore
Package objectstore provides a common S3-like storage abstraction used by handlers to work with real backends (Predastore) or in-memory stores for testing.
Package objectstore provides a common S3-like storage abstraction used by handlers to work with real backends (Predastore) or in-memory stores for testing.
otelsetup
Package otelsetup configures OpenTelemetry tracing and metrics for Mulga services.
Package otelsetup configures OpenTelemetry tracing and metrics for Mulga services.
qmp
services/qmpcollector
Package qmpcollector is the per-node guest-metrics producer (Goanna Phase 1): it discovers running VMs via their qmp-telemetry-*.json sidecar files, polls each VM's dedicated telemetry QMP socket (never the manager's control socket) plus host tap counters, and publishes CloudWatch-mappable series to NATS metrics.ec2.<instance-id>.
Package qmpcollector is the per-node guest-metrics producer (Goanna Phase 1): it discovers running VMs via their qmp-telemetry-*.json sidecar files, polls each VM's dedicated telemetry QMP socket (never the manager's control socket) plus host tap counters, and publishes CloudWatch-mappable series to NATS metrics.ec2.<instance-id>.
tags
Package tags defines tag keys for Spinifex system-owned resources.
Package tags defines tag keys for Spinifex system-owned resources.
testutil/vbscan
Package vbscan is a read-only storage-state oracle for viperblock volumes, driven directly over S3 rather than through any spinifex handler.
Package vbscan is a read-only storage-state oracle for viperblock volumes, driven directly over S3 rather than through any spinifex handler.
vm
tests
e2e/ddil
Package ddil is the root of the DDIL (Denied, Disrupted, Intermittent, Limited) E2E test harness.
Package ddil is the root of the DDIL (Denied, Disrupted, Intermittent, Limited) E2E test harness.
e2e/manifest-check
Package manifestcheck loads and validates spinifex/docs/service-interfaces.yaml.
Package manifestcheck loads and validates spinifex/docs/service-interfaces.yaml.
e2e/manifest-check/cmd/manifest-check command
Command manifest-check validates spinifex/docs/service-interfaces.yaml.
Command manifest-check validates spinifex/docs/service-interfaces.yaml.
e2e/manifest-lint
Package manifestlint implements the e2e manifest drift guards:
Package manifestlint implements the e2e manifest drift guards:
e2e/manifest-lint/cmd/manifest-lint command
Command manifest-lint runs the e2e manifest drift guards (Bead 5): fixture-create lint + NATS subject lint, both ratcheted against a checked-in baseline.
Command manifest-lint runs the e2e manifest drift guards (Bead 5): fixture-create lint + NATS subject lint, both ratcheted against a checked-in baseline.
e2e/select-suites
Package selectsuites derives the set of e2e suites a diff must exercise.
Package selectsuites derives the set of e2e suites a diff must exercise.
e2e/select-suites/cmd/select-suites command
Command select-suites prints the e2e suites a diff must run.
Command select-suites prints the e2e suites a diff must run.
fixtures/predastore
Package predastore starts a real predastore daemon for tests that need to exercise an actual S3-compatible backend rather than a mock.
Package predastore starts a real predastore daemon for tests that need to exercise an actual S3-compatible backend rather than a mock.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL