CloudLearn v1.2.5
Default-space naming convention. The three out-of-the-box spaces are now aws-default, gcp-default, and azure-default — matching how every other identifier in the appliance and SDK examples talks about per-provider defaults. Previous names (Legacy Workspace, GCP Project, Azure Subscription) were inconsistent and looked like manually-created spaces rather than defaults.
Changed
- Fresh installs now seed three spaces named
aws-default,gcp-default,azure-default(was:Legacy Workspace,GCP Project,Azure Subscription). Space IDs are unchanged (space-legacy,space-gcp-default,space-azure-default) socloudsim_runtime_id/lxd_project_namereferences in persisted state stay valid. - Existing installs get a one-shot migration on first v1.2.5 boot (
migrate_default_space_names()incore/app_context.py) — renames spaces only when the current name still matches the legacy default. Any space the user renamed themselves is untouched.
Why
The pricing/upgrade flow, the per-cloud console gates, and the docs all reference aws-default etc. as the canonical names. Having the UI show a different label was a needless source of "wait, which space am I in?" confusion for new users.
Artifacts
- SHA256SUMS
- cloud-learn-0.1.0.tar.gz
- cloud-learn-1.2.5-1.noarch.rpm
- cloud-learn-1.2.5.tar.gz
- cloud-learn_1.2.5_all.deb
Docker image: docker pull gansudkum/cloud-learn:1.2.5
Install: curl -fsSL https://raw.githubusercontent.com/sudhirkumarganti/cloud-learn/main/install.sh | bash
SHA256 checksums: see SHA256SUMS in attached artifacts.