Skip to content
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

Closed
lgj101 opened this issue Jul 18, 2022 · 5 comments · Fixed by kubevela/catalog#412
Closed

Error in Vela cli enabling velaux additional DEX parameters #4404

lgj101 opened this issue Jul 18, 2022 · 5 comments · Fixed by kubevela/catalog#412
Labels
area/addon priority/critical Highest priority. Must be actively worked on as someone's top priority right now. type/bug Something isn't working

Comments

@lgj101
Copy link
Contributor

lgj101 commented Jul 18, 2022

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)

image

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

@chivalryq
Copy link
Member

cc @FogDong

@chivalryq chivalryq added type/bug Something isn't working priority/critical Highest priority. Must be actively worked on as someone's top priority right now. area/addon labels Jul 18, 2022
@barnettZQG
Copy link
Collaborator

@lgj101 There is a way to bypass this issue. You can enable the VelaUX first, then set the DEX parameter via UI.

@lgj101
Copy link
Contributor Author

lgj101 commented Jul 18, 2022

@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

@barnettZQG
Copy link
Collaborator

barnettZQG commented Jul 18, 2022

@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

vela addon enable velaux dex="true"

@lgj101
Copy link
Contributor Author

lgj101 commented Jul 19, 2022

@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

vela addon enable velaux dex="true"

Can you do this over there? I still show the same error here, Or is it a version problem?

@lgj101 lgj101 closed this as completed Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/addon priority/critical Highest priority. Must be actively worked on as someone's top priority right now. type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants