In the platform-admin "all organizations" view, add an organization picker (the CreateOrgScopeField slot) to the SSH public key, storage type, storage, GPU instance and instance-template create forms, placed below the name / display-name fields. Drop the hidden owner field and let the owner derive from the request context, matching the model-route form. For GPU instances, scope the instance-type list to clusters the chosen org owns (client-side, by cluster owner) so an instance can't be scheduled onto another org's cluster; when the org owns none, show "no instance type available" and clear the selection, cluster and CPU/memory fields. Instance templates gain a Global level (NULL owner) and an owner tag on the card.
Adding a New Language Configuration
To add a new language configuration, follow these steps:
1. Duplicate an Existing Language Directory
- Choose any existing language directory that you are familiar with, and duplicate it.
- Name the new directory according to the
langattribute specified inlang-config-map.tsx.
2. Create a New .ts File in the Current Directory
- In the
localesdirectory, create a.tsfile named to align with the new directory. - Copy the contents of the
en-US.tsfile into this new.tsfile. - Update the following line to match your new language directory:
const requireContext = require.context( `./{new-language-directory}`, false, /\.ts$/ );
3. Translate Each Attribute Value
-
Open the
.tsfile in the new directory. -
For each key-value pair:
- If a translation is available, replace the value with the translated text.
- If no translation is available, keep the
Englishvalue as default.
-
Note: Keeping the English text as the default ensures the application remains functional even if some translations are missing.
4. Finalize the Configuration
- Review and ensure all translations are complete.
- If any translations are missing, they will default to
English. - Your new language configuration is now ready for use!
5. Verify that all language keys are consistent.
npm run check:locales