add description of extension lifecycle #387
Conversation
i18n/de/docusaurus-plugin-content-docs/current/contribution/30-overview/1-extensions.mdx
Outdated
Show resolved
Hide resolved
…-overview/1-extensions.mdx Co-authored-by: Ali Nazeri <[email protected]> Signed-off-by: tdellmann <[email protected]>
i18n/de/docusaurus-plugin-content-docs/current/contribution/30-overview/1-extensions.mdx
Outdated
Show resolved
Hide resolved
i18n/de/docusaurus-plugin-content-docs/current/contribution/30-overview/1-extensions.mdx
Outdated
Show resolved
Hide resolved
i18n/de/docusaurus-plugin-content-docs/current/contribution/30-overview/1-extensions.mdx
Outdated
Show resolved
Hide resolved
i18n/de/docusaurus-plugin-content-docs/current/contribution/30-overview/1-extensions.mdx
Outdated
Show resolved
Hide resolved
i18n/de/docusaurus-plugin-content-docs/current/contribution/30-overview/1-extensions.mdx
Outdated
Show resolved
Hide resolved
| A graceful deletion of the extension can be realized through defining a deprecation. | ||
| The Deprecation defines a shut down date as well as a successor. | ||
|
|
||
| The deletion of the Extension is asynchronous because all Extension-Instances must be removed beforehand. |
There was a problem hiding this comment.
This is inconsistent with the german translation ("Die Löschung der Extension passiert asynchron, weil alle Extension-Instances vorab gelöscht werden.").
The original sentence ("must be removed") implies that some kind of action is required (either from the contributor, or from the extension users) to remove existing extension instances, whereas the passive phrasing in the german version implies that this is done by the system.
Which is it?
There was a problem hiding this comment.
the german version is correct. That concept changed while this was worked on.
I'm going to correct this.
| @@ -77,6 +77,48 @@ Optionally, an extension may define an external frontend that functions as an en | |||
| You configure the external frontend as a URL, for which you may use templating. | |||
| For more information, see [templating of configuration values](../concepts/templating) and [lifecycle webhook concept](../concepts/lifecycle-webhooks). | |||
|
|
|||
| ## Lifecycle of an Extension | |||
|
|
|||
| After registering an Extension the verification can be requested. | |||
There was a problem hiding this comment.
I get that this is a high-level description of the whole process; but is there a more detailed description of the whole process (including API calls and such) somewhere that we can link here?
There was a problem hiding this comment.
not yet, unfortunately.
The routes are currently beeing beautified before we publish them.
Co-authored-by: Martin Helmich <[email protected]> Signed-off-by: tdellmann <[email protected]>
No description provided.