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

Allow for more fine tune provisioning options #1807

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

Allow for more fine tune provisioning options #1807

wants to merge 3 commits into from

Conversation

AZaugg
Copy link

@AZaugg AZaugg commented Mar 12, 2020

Allow a user to better control what WAAgent provisions during a
Provisioning event. Allow the user to control if, useraccounts, hostname
and custom data be set.

Description

Issue #


PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes in the description.
  • New Unit tests were added for the changes made and Travis.CI is passing.

Quality of Code and Contribution Guidelines


This change is Reviewable

@msftclas
Copy link

msftclas commented Mar 12, 2020

CLA assistant check
All CLA requirements met.

@vrdmr
Copy link
Member

vrdmr commented Mar 17, 2020

@anhvoms @trstringer - Could you please take a look at this? This is from the offline discussion you had with @AZaugg.

@vrdmr vrdmr removed their request for review April 23, 2020 00:05
anhvoms
anhvoms previously approved these changes Jun 23, 2020
trstringer
trstringer previously approved these changes Jun 23, 2020
@trstringer trstringer self-requested a review June 23, 2020 17:41
Allow a user to better control what WAAgent provisions during a
Provisioning event. Allow the user to control if, useraccounts, hostname
and custom data be set.
AZaugg and others added 2 commits November 9, 2020 15:00
Allow a user to better control what WAAgent provisions during a
Provisioning event. Allow the user to control if, useraccounts, hostname
and custom data be set.
_Type: Boolean_
_Default: y_

Control if WAAgent should attempt to set the VMs hostname
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you explain when this would be used? Perhaps add an example for when you would want to change from the default and not set the hostname.

Nit: periods at the end of the sentence for document consistency.

_Type: Boolean_
_Default: y_

Control if WAAgent should configure user accounts
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above. Maybe add an example usage when you wouldn't want to configure user accounts.

Nit: period at the end of the sentence for consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants