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

Tink CLI - create sample configuration #334

Closed
thebsdbox opened this issue Oct 9, 2020 · 1 comment
Closed

Tink CLI - create sample configuration #334

thebsdbox opened this issue Oct 9, 2020 · 1 comment
Labels
area/tink-cli help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/S estimate of the amount of work to address the issue

Comments

@thebsdbox
Copy link
Contributor

Expected Behaviour

The cli provides the capability to generate sample output that an end user can easily take as a starting point to modifying and customise to their own needs.

In Kubernetes an end user can accomplish something similar with the --dry-run flag that will create output instead of applying or creating a configuration.

$ kubectl create deployment my-dep --image=nginx --dry-run=client -o json
{
  ...
}

An additional benefit is that this would always generate output that matches the specification of the structs in the tinkerbell server.

Current Behaviour

An end user has to take a large amount of json or yaml from docs and modify it to their own needs. We've seen issues where the docs haven't reflected changes to the yaml/json spec resulting in broken deployments.

Context

Simplify the UX for the end user

@thebsdbox thebsdbox added kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. size/S estimate of the amount of work to address the issue area/tink-cli labels Oct 9, 2020
@tstromberg tstromberg added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 27, 2021
@jacobweinstock
Copy link
Member

closed by #654

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tink-cli help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. size/S estimate of the amount of work to address the issue
Projects
None yet
Development

No branches or pull requests

3 participants