Reference
Object storage / Managed object storage
Provision a private Spaces bucket for application assets, backups, and file storage under one project.
Overview
Variant overview
Provision a private Spaces bucket for application assets, backups, and file storage under one project.
Manifest file
Edit object-storage-spaces.environment.yaml to change the scenario.
Rendered output
OPSd renders the manifest into OpenTofu under rendered/object-storage-spaces.
Supported changes
The variant defines which add, remove, and scale operations are supported.
Good fit
the operating model of this variant already matches the team and workload
Tradeoff
Review the supported growth boundary before choosing this path.
What gets created for this setup
This diagram shows the result you get after rendering the selected variant.
Infrastructure shape
Before you start
Shared setup is covered in Installation and the Introduction. This section lists the minimum things you need before the first render for DigitalOcean.
- Installation install the shared OPSd CLI.
- Introduction understand the workflow boundary and required toolchain.
- Have a container image or build artifact ready.
Initialize this variant
This is the first-run path when no scenario has been initialized yet.
Initialization sequence
opsd list blueprints
opsd init blueprint object-storage object-storage-spaces.environment.yaml --variant spaces
opsd validate manifest object-storage-spaces.environment.yaml
opsd render manifest object-storage-spaces.environment.yaml --output rendered/object-storage-spaces
cd rendered/object-storage-spaces
tofu init
tofu plan
# review the rendered output before planning
cd rendered/object-storage-spaces
tofu init
tofu plan Edit the manifest
After the first deployment, the supported path is still manifest first. Use the supported opsd add, remove, and scale commands for this variant, then validate and render again.
Supported change commands
Add a CDN endpoint
Add a CDN-backed endpoint for public assets.
opsd add cdn-endpoint object-storage-spaces.environment.yaml --origin assets-main --id assets-cdn Edit, validate, render
# edit object-storage-spaces.environment.yaml
# validate the config before rendering
opsd validate manifest object-storage-spaces.environment.yaml
# render the updated output and review it
opsd render manifest object-storage-spaces.environment.yaml --output rendered/object-storage-spaces
cd rendered/object-storage-spaces
# plan and apply only after the diff is clear
tofu plan
tofu apply Supported changes
These examples come from the variant capability map and show the supported add, remove, and scale operations for this setup.
Add a CDN endpoint
Add a CDN-backed endpoint for public assets.
opsd add cdn-endpoint object-storage-spaces.environment.yaml --origin assets-main --id assets-cdn Changes are not active yet
Editing the manifest changes the desired state. To make it real, validate the manifest, render the updated output, and then run `tofu apply` against the rendered directory.
opsd validate manifest object-storage-spaces.environment.yaml
opsd render manifest object-storage-spaces.environment.yaml --output rendered/object-storage-spaces
cd rendered/object-storage-spaces
tofu plan
tofu apply Related variants
Use the scenario overview to compare the other supported variants for the same blueprint.