paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 21 Packages Projects Releases Wiki Activity

Merge pull request #9270 from backstage/freben/callouts

Browse Source 
fix callouts
This commit is contained in:
Johan Haals
2022-01-31 10:39:57 +01:00
committed by GitHub
parent 20d9579a88 c710467ba2
commit e8445a15a1
1 changed files with 5 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/software-catalog/api.md
+5 -13
View File
@@ -12,12 +12,8 @@ by external systems. This page describes its shape and features.
The API surface consists of a few distinct groups of functionality. Each has a
dedicated section below.
{% note %}
**Note:** This page only describes some of the most commonly used parts of the
API, and is a work in progress.
{% endnote %}
> **Note:** This page only describes some of the most commonly used parts of the
> API, and is a work in progress.
All of the URL paths in this article are assumed to be on top of some base URL
pointing at your catalog installation. For example, if the path given in a
@@ -199,13 +195,9 @@ error if there was no entity with that UID.
Deletes an entity by its `metadata.uid` field value.
{% note %}
**Note:** This method of deletion is appropriate for orphaned entities, but not
for removal of "live" entities that are actively being updated by a location.
Please read below.
{% endnote %}
> **Note:** This method of deletion is appropriate for orphaned entities, but
> not for removal of "live" entities that are actively being updated by a
> location. Please read below.
The most common user flow is that you register a location (see below), and then
the catalog keeps itself up to date with that location and the subtree of things