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

[ENHANCEMENT] Replace DaC init script by percli dac setup #1695

Merged
merged 10 commits into from
Jan 17, 2024

Conversation

AntoineThebaud
Copy link
Contributor

@AntoineThebaud AntoineThebaud commented Jan 10, 2024

Description

dac_setup.sh script replaced by a new CLI command percli dac setup.

Checklist

  • Pull request has a descriptive title and context useful to a reviewer.
  • Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
    following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
  • All commits have DCO signoffs.

Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
@AntoineThebaud AntoineThebaud marked this pull request as ready for review January 11, 2024 13:52
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
@AntoineThebaud AntoineThebaud changed the title Replace DaC init script by new CLI command [ENHANCEMENT] Replace DaC init script by new CLI command Jan 12, 2024
@AntoineThebaud AntoineThebaud changed the title [ENHANCEMENT] Replace DaC init script by new CLI command [ENHANCEMENT] Replace DaC init script by percli dac setup Jan 12, 2024
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
return persesCMD.Run(o, cmd, args)
},
}
cmd.Flags().StringVar(&o.version, "version", "", "Version of Perses from which to retrieve the CUE dependencies.")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we should manage the setup for the go sdk as well here. That's kind of weird from my point of view the command dac init would support only one language

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO better to keep it simple thus CUE-opinionated for now, and to refactor with a next PR when we'd want to make it work with the Go SDK, but that's a matter of preference I guess.

Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
Signed-off-by: Antoine THEBAUD <antoine.thebaud@yahoo.fr>
return nil
}

func (o *option) Validate() error {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you think about checking if the binary cue is accessible. I'm thinking also we could provide a flag that will give us the path to the binary cue. So you can point exactly what binary you want to use and also in case cue is not in the PATH

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's do that in a different PR. It's actually not that simple.

Copy link
Member

@Nexucis Nexucis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well done ! 🥳

@Nexucis Nexucis merged commit fdf709e into feat/dashboard-as-code Jan 17, 2024
18 checks passed
@Nexucis Nexucis deleted the antoinethebaud/DaC-part2 branch January 17, 2024 10:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants