Portals should enable users to self provisioning resources using the Terraform modules published in the Terrakube private registry. The UI Should provide a similar experience to GCP console, Azure portal, AWS console. Portals should be an abstraction to final customer to provision resources without the specific knowledge about terraform concepts creating a real cloud agnostic self provisioning experience.
Basically inside each organization the admin can define multple portals. The following fields are required:
Id: a UID
Name: The portal name
Services: Multiple services can be selected.
A service is an abstraction of a terraform module. The API and UI should provide the following fields:
Id: UID for the service
Name: Friendly name of the service, example MySQL, Prometheus, etc
Icon: An icon for the service
Terraform Module: Id of the Terraform module published in Terrakube registry
Create Template: Id of the template to use during the creation
Delete Template: Id of the template to use during deletion
Update Template: Id of the template to use during Update
View Templates: Array with additional templates to show in the resource view.
Once the customer access the Portal, will see the list of services for the specific portal. When the user select to create a new service, then a new form will appear with all the fields based on the Terraform module variables.
Initially this can be free textbox, but in the future will be possible to map each field with a textbox type.
When the user provision a new service a new workspace will be created in Terrakube and will execute the specific template.
jcanizalez
commented
1 year ago
Feature description 💡
Overview
Portals should enable users to self provisioning resources using the Terraform modules published in the Terrakube private registry. The UI Should provide a similar experience to GCP console, Azure portal, AWS console. Portals should be an abstraction to final customer to provision resources without the specific knowledge about terraform concepts creating a real cloud agnostic self provisioning experience.
Basically inside each organization the admin can define multple portals. The following fields are required:
A service is an abstraction of a terraform module. The API and UI should provide the following fields:
Once the customer access the Portal, will see the list of services for the specific portal. When the user select to create a new service, then a new form will appear with all the fields based on the Terraform module variables. Initially this can be free textbox, but in the future will be possible to map each field with a textbox type.
When the user provision a new service a new workspace will be created in Terrakube and will execute the specific template.
Anything else?
No response