9
2
Fork
You've already forked platform
2

rename byoc to bring your own compute #300

Manually merged
ryansquared merged 2 commits from xenushka/rename-byoc into main 2026年06月22日 06:14:12 +02:00
No description provided.
@ -690,3 +690,3 @@
TEST_DATABASE_URL := postgresql://$(DB_USER):$(DB_PASSWORD)@$(TEST_DB_HOST):5432/$(TEST_DB_NAME)
E2E_LOCK_FILE ?= /tmp/caution-platform-e2e.lock
ONPREM_PROVISIONER_DIR ?= ../bring-your-own-cloud-setup
ONPREM_PROVISIONER_DIR ?= ../bring-your-own-compute-setup
Owner
Copy link

Has not been renamed on the codeberg repo https://codeberg.org/caution/bring-your-own-cloud-setup

Has not been renamed on the codeberg repo https://codeberg.org/caution/bring-your-own-cloud-setup
ryansquared marked this conversation as resolved
@ -56,3 +56,3 @@
constBYOC_PROVISIONER_IMAGE: &str =
"codeberg.org/caution/caution-managed-on-prem-aws-provisioner:latest";
constBYOC_STATE_FILE_NAME: &str ="bring-your-own-cloud.json";
constBYOC_STATE_FILE_NAME: &str ="bring-your-own-compute.json";
Owner
Copy link

⚠️ any user who ran caution init --byoc before this change has a bring-your-own-cloud.json on disk, after upgrading, caution teardown --byoc won't find it → orphaned AWS resources that can't be torn down (and keep billing)

⚠️ any user who ran caution init --byoc before this change has a bring-your-own-cloud.json on disk, after upgrading, caution teardown --byoc won't find it → orphaned AWS resources that can't be torn down (and keep billing)
Owner
Copy link

commit below 616992f9bc fixes this and will also look for the former file name on teardown

commit below 616992f9bc fixes this and will also look for the former file name on teardown
ryansquared marked this conversation as resolved
ryansquared manually merged commit 03658d917c into main 2026年06月22日 06:14:12 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Component/Enclave-Builder
This issue affects Enclave Builder (git-push and CLI)
Component/Infrastructure
This issue affects generic Caution hosted infra components
Deploy/BYOC
Relates to Caution Bring-your-own-compute
Deploy/Full-managed
Relates to Caution fully managed cloud
Deploy/Self-hosted
Relates to Caution deployed on self-hosted infra
Interface/API
This issue affects the API
Interface/CLI
This issue affects the command line interface
Interface/Git
This issue affects the Git `push` interface
Interface/Web
This issue affects the web dashboard
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
 The priority is critical
Priority
High
 The priority is high
Priority
Low
 The priority is low
Priority
Medium
 The priority is medium
Reviewed
Confirmed
 Issue has been confirmed
Reviewed
Duplicate
 This issue or pull request already exists
Reviewed
Invalid
 Invalid issue
Reviewed
Won't Fix
 This issue won't be fixed
Status
Abandoned
 Somebody has started to work on this but abandoned work
Status
Blocked
 Something is blocking this issue or pull request
Status
Need More Info
 Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
caution/platform!300
Reference in a new issue
caution/platform
No description provided.
Delete branch "xenushka/rename-byoc"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?