Components installed with AES
Summarize
Summary of Components installed with AES
Activating the App Engine Studio (AES) plugin installs various components, including tables and user roles, essential for managing and building applications within AES. These components support application development, deployment, user access control, and help resource management.
Show less
Roles Installed
- App Engine admin [appengineadmin]: Manages AES users, app configuration, and administration tasks. Assigned automatically to users in the App Engine Studio Admins group.
- App Engine Studio app template admin [apptemplateadmin]: Controls use, sharing, and activation/deactivation of templates. Assigned manually by an admin.
- App Engine Studio admin [snappengstudio.admin]: Provides granular administrative access to AES and related tables, allowing combination with other granular admin roles for enhanced permissions.
- App Engine Studio user [snappengstudio.user]: Enables users to build applications in AES. Automatically assigned to users in the App Engine Studio Users group.
Additional granular admin roles come with dependent applications, such as Collaboration Request Admin and AES Table Builder Wizard Admin, allowing tailored access based on user responsibilities.
Tables Installed
Several tables are installed to support AES operations, including:
- App Details: Tracks developer actions during app creation.
- Applications in Projects: Lists applications created within AES projects.
- Environment: Defines instances used for development, testing, and launching applications.
- Deployment Request: Manages application review and deployment requests, enabling reviewers to deploy or provide feedback.
- Pipeline: Configures deployment pipelines; only one pipeline is active at a time.
- Project: Stores details about development sessions and projects created automatically.
- Resources Content and Topic: Contains help resources and their categorizations to enhance user experience.
- Taxonomy and related tables: Manage application file categorizations and details, supporting default AES user experience.
Data preservers are added to pipeline-related tables to prevent data overwriting during cloning on non-production instances, ensuring deployment configurations remain intact.
Several types of components are installed with activation of the App Engine Studio (AES) plugin, including tables and user roles.
Roles installed
| Role title [name] | Description | Contains roles |
|---|---|---|
App Engine admin [app_engine_admin] |
Administers AES, including users, app configuration, and other management tasks. This role is assigned automatically to users in the App Engine Studio Admins group. |
|
App Engine Studio app template admin [app_template_admin] |
Administers the use, sharing, and activation or deactivation of templates. This role is assigned by an admin to individual users. For more information, see Manage template access. |
|
|
App Engine Studio admin [sn_app_eng_studio.admin] |
Granular admin role that grants access to App Engine Studio and enables administrative access to App Engine Studio tables. You can combine this role with other granular admin roles or delegated development for additional permissions. For more information about granular admin roles, see Granular admin roles required to secure your instance. | sn_app_eng_studio.user |
App Engine Studio user [sn_app_eng_studio.user] |
Builds applications in App Engine Studio. This role is assigned automatically to users in the App Engine Studio Users group. For more information, see Grant user access to AES. |
|
- Collaboration request admin [sn_collab_request.collaboration_request_admin]
- AES Table Builder Wizard admin [sn_table_bldr_wzd.table_bldr_wzd_admin]
Tables installed
| Table | Description |
|---|---|
App Details [sn_app_eng_studio_app_details] |
Details about the operations that a developer used to create an application in App Engine Studio. The table is updated automatically as developers build applications in App Engine Studio. |
Applications in Projects [sn_app_eng_studio_project_application_m2m] |
Applications that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. |
Environment [sn_pipeline_environment] |
Instances that you use for the developing, testing, or launching an application. You update this table as you define environments for App Engine Studio. |
Deployment Request [sn_deploy_pipeline_deployment_request] |
Requests to review and publish an application that a developer created in App Engine Studio. From the deployment request form, a reviewer can deploy the application to different environments, accept or reject an application, and send feedback to a developer. For more information, see Deployment Request form in the Pipelines and Deployments app. |
Pipeline [sn_pipeline_pipeline] |
Configurations for deploying applications to different environments. Only one pipeline can be active at a time. You update this table as you create a pipeline for the deployment of applications from App Engine Studio. For more information, see Managing deployments using Pipelines and Deployments. |
Project [sn_app_eng_studio_project] |
Details about App Engine Studio development sessions. A project is created automatically when a developer creates an application in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. |
Resources Content [sn_app_eng_studio_resources_content] |
Help resources that a developer can access in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. |
Resources Content Topic [sn_app_eng_studio_resources_content_topic] |
Categorizations of help resources in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. |
Taxonomy [sn_app_eng_studio_taxonomy] |
Application files that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. |
Taxonomy Category [sn_app_eng_studio_taxonomy_category] |
Categorizations for application files in App Engine Studio. By default, application files are categorized as data, experience, logic and automation, or security. This table includes configurations to support the default user experience for App Engine Studio. |
Taxonomy Details [sn_app_eng_studio_taxonomy_details] |
Details about application files that a developer creates in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. |
- Environment
- Pipeline
- Pipeline Environment Order
- Pipeline Types
The data preservers prevent records in these tables from being overwritten during cloning on a non-production instance. For more information, see Create a clone preserver.