Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Include more information about the policy in chef push output #1704

Merged
merged 1 commit into from
Sep 18, 2018

Conversation

danielsdeleo
Copy link
Contributor

@danielsdeleo danielsdeleo commented Sep 18, 2018

Description

The goal of this change is to surface more information so that it's
easier for users to detect a certain class of mistakes (e.g., run
chef push from the wrong working directory) and to produce a more
useful log of what chef push did when run in a Ci context.

Possible downside is that the extra information may be offputting to
novice users, but that's probably a wash as some novices would likely
appreciate the additional detail about the consequences of the command
they are running.

Old output:

Uploading policy to policy group new_pgroup
< other stuff >

New output:

Uploading policy jenkins (d064016951) to policy group new_pgroup
< other stuff >

Issues Resolved

Inspired by a debugging session in Chef Software internal slack.

Check List

@danielsdeleo danielsdeleo requested a review from a team September 18, 2018 17:37
@tas50
Copy link
Contributor

tas50 commented Sep 18, 2018

@danielsdeleo Specs are mad

The goal of this change is to surface more information so that it's
easier for users to detect a certain class of mistakes (e.g., run
`chef push` from the wrong working directory) and to produce a more
useful log of what `chef push` did when run in a Ci context.

Possible downside is that the extra information may be offputting to
novice users, but that's probably a wash as some novices would likely
appreciate the additional detail about the consequences of the command
they are running.

Signed-off-by: Daniel DeLeo <dan@chef.io>
@danielsdeleo
Copy link
Contributor Author

@tas50 derp, did a small reorganization and forgot to re-run. Should be fine now

@danielsdeleo danielsdeleo merged commit 41f0e0d into master Sep 18, 2018
@chef-ci chef-ci deleted the dan/more-verbose-push branch September 18, 2018 21:30
@lock
Copy link

lock bot commented Nov 17, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants