Skip to content

Commit f363a56

Browse files
Unmentioning the Typescript and Starlak SDKs
Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
1 parent 126368a commit f363a56

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

profile/README.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,7 @@ We have a kpt users [mailing list](https://groups.google.com/forum/?oldui=1#!for
4545
they are expected to be used for in-place transformation, the functions need to be idempotent.
4646
- [krm-function-sdk](https://github.com/kptdev/krm-functions-sdk): Any general-purpose or domain-specific language can
4747
be used to create functions to transform and/or validate the YAML KRM input/output format, but we provide SDKs to
48-
simplify the function authoring process, in [Go](https://kpt.dev/book/05-developing-functions/02-developing-in-Go),
49-
[Typescript](https://kpt.dev/book/05-developing-functions/03-developing-in-Typescript), and
50-
[Starlark](https://kpt.dev/book/05-developing-functions/04-developing-in-Starlark), a Python-like embedded language.
48+
simplify the function authoring process in [Go](https://kpt.dev/book/05-developing-functions/02-developing-in-Go).
5149
- [kpt-backstage-plugins](https://github.com/kptdev/kpt-backstage-plugins): We've created a proof-of-concept UI in the
5250
form of a [Backstage UI plugin](https://github.com/kptdev/kpt-backstage-plugins) to demonstrate the WYSIWYG
5351
experience that's possible on top of the package orchestrator. More scenarios can be supported by implementing

0 commit comments

Comments
 (0)