Release Notes v0.75

Release v0.75 introduces Resource Mapping to Project Types, offering companies greater control over resource visibility and management, as well as some enhancements and bug fixes.

✨ What's New

Map Resources to Project Type:
You can now define exactly which resources belong in each project type, ensuring only approved resources are accessible in a project's resource list.

• After creating a project type, click Manage Resources to view available intents and flavors and select the ones that meet your requirements.
• While creating a project from a project type, you can now view all permitted modules for the selected project type upfront.
• Once the project is created, the project's resource list reflects the selections tied to the project type.

Example Use Case: Suppose you want to restrict the use of a specific MongoDB flavor, like Atlas, in projects tied to a particular project type.

In that case as an admin, you can navigate to the Project Types list screen, click on "Manage Resources" of the respective project type and uncheck the Atlas flavor under the MongoDB intent, save your changes, and you’re set.

Later, if that flavor is needed, you can always edit the resource list linked to that project type to re-include it, without needing to create a new project type from scratch.

See it in Action:

📈 Enhancements

• Users can mark any project as a "Testing Project" from Project Setting. If enabled, all the preview registered modules will also be available in the resource list which can be added in the blueprint.
• Users will now be able to register modules with user-defined Intents as well.
• Users will now be able to send an optional git commit id and its web url as metadata when registering the module with facets. This will allow users to navigate to that module's source code in git from the UI. which will be shown on the UI, to keep a link between the uploaded module and its source code in Git.