Merge pull request #16159 from waldirmontoya25/master

Update the ecosystem model section of the docs
This commit is contained in:
Ben Lambert
2023-02-09 09:38:04 +01:00
committed by GitHub
4 changed files with 31 additions and 2 deletions
File diff suppressed because one or more lines are too long

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 23 KiB

File diff suppressed because one or more lines are too long

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 52 KiB

@@ -63,6 +63,17 @@ BigTable databases, Pub/Sub topics, S3 buckets or CDNs. Modelling them together
with components and systems will better allow us to visualize resource
footprint, and create tooling around them.
##Organizational Entities
### User
A user describes a person, such as an employee, a contractor, or similar.
### Group
A group describes an organizational entity, such as for example a team, a
business unit, or a loose collection of people in an interest group.
## Ecosystem Modeling
A large catalogue of components, APIs and resources can be highly granular and
@@ -108,3 +119,19 @@ domain would come with some documentation on how to accept payments for a new
product or use-case, share the same entity types in their APIs, and integrate
well with each other. Other domains could be “Content Ingestion”, “Ads” or
“Search”.
##Other
### Location
A location is a marker that references other places to look for catalog data.
### Type
The type field in the system has no set meaning. It is up to the user to assign their own types and use them as desired, such as for link validation or creating custom UI components. Some common pre-defined types are depicted in the ecosystem modeling diagram.
### Template
A template definition describes both the parameters that are rendered in the
frontend part of the scaffolding wizard, and the steps that are executed when
scaffolding that component.
+2
View File
@@ -34,6 +34,8 @@ The permission framework was designed with a few key properties in mind:
4. An authorization decision is sent to the plugin from the permission backend.
5. The user is either granted access or an error is shown. The plugin is responsible for implementing a response to the user.
## How do I get started?
See the "[getting started](./getting-started.md)" permission documentation for Backstage integrators.