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

Return node object as part of chef-run execution #136

Open
tyler-ball opened this issue Jun 23, 2020 · 0 comments
Open

Return node object as part of chef-run execution #136

tyler-ball opened this issue Jun 23, 2020 · 0 comments
Labels
Aspect: Integration Works correctly with other projects or systems. Aspect: UX How users feel interacting with the project, focusing on function, ease-of-use and accessibility. Triage: Feature Request Indicates an issue requesting new functionality. Type: Design Proposal Community survey of a proposal.

Comments

@tyler-ball
Copy link
Contributor

Describe the Enhancement:

Customers have expressed a desire to use the state of a node as part of control flow. EG, if the node is a Windows machine perhaps they use that information to kick off a second chef-run execution.

Describe the Need:

Return the node data (the node.json that gets sent to the Chef Server) to the workstation after completing the chef-run execution.

Current Alternative

Querying this with knife. Manually looking it up on the Chef Server, EG via knife search.

Neither of these options work in a non-Chef-Server environment, thus the desire to return this information from chef-run

Questions

  1. What would the UX for this look like?
  2. Could we coordinate returning this information as part of Copy chef-client run output to host #135? Perhaps they end up in a shared folder, or part of a shared zip?
@tyler-ball tyler-ball added Status: Untriaged An issue that has yet to be triaged. Aspect: Integration Works correctly with other projects or systems. Aspect: UX How users feel interacting with the project, focusing on function, ease-of-use and accessibility. Triage: Feature Request Indicates an issue requesting new functionality. Type: Design Proposal Community survey of a proposal. and removed Status: Untriaged An issue that has yet to be triaged. labels Jun 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aspect: Integration Works correctly with other projects or systems. Aspect: UX How users feel interacting with the project, focusing on function, ease-of-use and accessibility. Triage: Feature Request Indicates an issue requesting new functionality. Type: Design Proposal Community survey of a proposal.
Projects
None yet
Development

No branches or pull requests

1 participant