Skip to content

vic-machine: Fix message from inspect config#7544

Merged
zjs merged 2 commits intovmware:masterfrom
zjs:topic/inspect-message
May 14, 2018
Merged

vic-machine: Fix message from inspect config#7544
zjs merged 2 commits intovmware:masterfrom
zjs:topic/inspect-message

Conversation

@zjs
Copy link
Member

@zjs zjs commented Mar 19, 2018

The vic-machine inspect config command describes the current state of the target VCH. When this command was implemented, this was equivalent to the options used to create the VCH. Since then, the
vic-machine configure command has been added. This change corrects the phrasing of the message to clearly communicate that the output is the current state of the VCH, not the initial creation options.

The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.
@zjs zjs added area/cli The Vritual Container Host management CLI (vic-machine) component/install team/lifecycle labels Mar 19, 2018
@zjs zjs self-assigned this Mar 19, 2018
Copy link
Contributor

@cgtexmex cgtexmex left a comment

Choose a reason for hiding this comment

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

Thanks!

Copy link
Contributor

@mhagen-vmware mhagen-vmware left a comment

Choose a reason for hiding this comment

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

lgtm

@codecov-io
Copy link

codecov-io commented Mar 19, 2018

Codecov Report

Merging #7544 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7544   +/-   ##
=======================================
  Coverage   26.34%   26.34%           
=======================================
  Files          37       37           
  Lines        5189     5189           
=======================================
  Hits         1367     1367           
  Misses       3715     3715           
  Partials      107      107

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 71664a5...23fb052. Read the comment docs.

Copy link
Member Author

@zjs zjs left a comment

Choose a reason for hiding this comment

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

Before submitting, I should ensure that we have a test case which verifies that this output is indeed updated following a configure operation.

@zjs zjs added this to the Sprint 29 Lifecycle milestone Mar 28, 2018
@zjs zjs merged commit 7662397 into vmware:master May 14, 2018
zjs added a commit to zjs/vic that referenced this pull request Jun 21, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit to zjs/vic that referenced this pull request Jun 22, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit to zjs/vic that referenced this pull request Jun 28, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit to zjs/vic that referenced this pull request Jul 2, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit to zjs/vic that referenced this pull request Jul 2, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit to zjs/vic that referenced this pull request Jul 12, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit to zjs/vic that referenced this pull request Jul 27, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
zjs added a commit that referenced this pull request Jul 27, 2018
The `vic-machine inspect config` command describes the current state
of the target VCH. When this command was implemented, this was
equivalent to the options used to create the VCH. Since then, the
`vic-machine configure` command has been added. This change corrects
the phrasing of the message to clearly communicate that the output is
the current state of the VCH, not the initial creation options.

(cherry picked from commit 7662397)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/cli The Vritual Container Host management CLI (vic-machine) cla-not-required component/install team/lifecycle

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants