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
currently ,we can support launching the corresponding app through ClusterSpec.APPNames,
Or directly use ClusterSpec.CMD to overwrite the app launch cmds.
however, for different types of apps, we have different startup commands and launch files, could we precisely support the configuration of the app at run stage?
so i proposal that we could add Application kind as below, for extensibility supporting config the sealer app and enrich the clusterfile's capabilities
for app files: We can modify the app file content according to the specified file path, such as overwrite,merge,render.
for app launch and delete: We can configure the corresponding launch or delete depending on the type of app, such as helm,kube,shell. At the same time, we can also support the raw launch command line.
for cmds and appNames they are mutually exclusive, could be overwrite from clusterspec and cli flags. 4. for env its a global key pair used to do render(kube),export shell env(shell), set values.yaml(helm).
Issue Description
Type: feature request
Describe what feature you want
currently ,we can support launching the corresponding app through
ClusterSpec.APPNames
,Or directly use
ClusterSpec.CMD
to overwrite the app launch cmds.however, for different types of apps, we have different startup commands and launch files, could we precisely support the configuration of the app at run stage?
so i proposal that we could add
Application
kind as below, for extensibility supporting config the sealer app and enrich the clusterfile's capabilitiesoverwrite
,merge
,render
.helm
,kube
,shell
. At the same time, we can also support the raw launch command line.4. for env its a global key pair used to do render(kube),export shell env(shell), set values.yaml(helm).Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: