You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the next version I plan to add initial support to manage KPS in the same way as other entities. This means to provide the following features:
#478
Open
acirami opened this issue
Apr 12, 2024
· 2 comments
@cwiechmann
What happen to this? I don't see support for KPS?
With the next version I plan to add initial support to manage KPS in the same way as other entities. This means to provide the following features:
get existing entries (Console, JSON, CSV, etc.) from a given table/alias
Filter support
import/replicate KPS entries based on JSON desired state
to replicate the KPS-ID is used to decide if update or create an entry
the desired state may contain multiple KPS Tables/Aliases and entries for each
delete entries based on the given filter
In the version after KPS-Dependencies can be added to an API. This dependency will be the KPS-Alias plus the Entry-ID. This kind of fragment will then be added to an API on the root level:
With that, during replication of an API the CLI validates that the required KPS entries do exists. The required KPS entries must be imported before using the KPS import feature added with the next version.
The KPS dependency information is planned to be stored in a custom property and based on that also exported.
@cwiechmann
What happen to this? I don't see support for KPS?
In the version after KPS-Dependencies can be added to an API. This dependency will be the KPS-Alias plus the Entry-ID. This kind of fragment will then be added to an API on the root level:
With that, during replication of an API the CLI validates that the required KPS entries do exists. The required KPS entries must be imported before using the KPS import feature added with the next version.
The KPS dependency information is planned to be stored in a custom property and based on that also exported.
Originally posted by @cwiechmann in #6 (comment)
The text was updated successfully, but these errors were encountered: