-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in Vela cli enabling velaux additional DEX parameters #4404
Comments
cc @FogDong |
@lgj101 There is a way to bypass this issue. You can enable the VelaUX first, then set the DEX parameter via UI. |
Thank you, I saw this in the document, but I want to start single sign on by default. After all, DEX parameters are also allowed to be configured here |
|
Can you do this over there? I still show the same error here, Or is it a version problem? |
Describe the bug
When velaux is enabled with Vela cli, the following error occurs when you want to configure the DEX parameter to true,
To Reproduce
vela addon enable velaux dex=true
{"level":"info","ts":1658135083.7932477,"caller":"addon/versioned_registry.go:210","msg":"Not specified any version, so use the latest version v1.4.6"}
Error: render addon application fail: fail to render cue template yaml: unsupported node <[l2// from source] |> (*ast.BottomLit)
Expected behavior
As long as the DEX parameter is added, this problem will occur, but this parameter is configurable. Shouldn't this be the case
KubeVela Version
CLI Version: v1.4.6
Core Version: 1.4.2
GitRevision: git-dfe12cd
GolangVersion: go1.17.11
The text was updated successfully, but these errors were encountered: