Chapter 4. Configuring template RBAC and display logic
Template definitions in the YAML file control where templates appear in the self-service automation portal and how to manage permissions.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
4.1. Role-based access control (RBAC) リンクのコピーリンクがクリップボードにコピーされました!
The template type determines where you must configure user permissions.
- Auto-generated templates: Permissions synchronize from Ansible Automation Platform. Users must have permissions on the underlying Ansible Automation Platform job template. For more information, see Setting up initial RBAC rules in self-service automation portal.
- Custom templates: You must explicitly configure permissions within the self-service automation portal. Users must also have permission to run the associated job templates in Ansible Automation Platform. For more information see, Setting up RBAC for custom self-service templates.
4.2. Backstage software template display logic (spec.type) リンクのコピーリンクがクリップボードにコピーされました!
The spec.type value in the template YAML determines which portal page displays the template.
- No spec.type defined: The template appears on the Ansible Automation Platform templates page for all users.
- spec.type: execution-environment: The template appears only on the EE definition files page.
4.3. Example: Auto-generated template リンクのコピーリンクがクリップボードにコピーされました!
The following YAML example uses the spec.type field to restrict the template view to the EE definition files page.