remove experimental warning from become/runas (#32604)

* updated docs/changelog accordingly
This commit is contained in:
Matt Davis 2017-11-06 15:37:45 -08:00 committed by GitHub
parent 8b3ca4c537
commit 8a24116dcb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 2 additions and 6 deletions

View file

@ -82,6 +82,7 @@ Ansible Changes By Release
- TODO: build upon this to add many features detailed in ansible-config proposal https://github.com/ansible/proposals/issues/35 - TODO: build upon this to add many features detailed in ansible-config proposal https://github.com/ansible/proposals/issues/35
* Windows modules now support the use of multiple shared module_utils files in the form of Powershell modules (.psm1), via `#Requires -Module Ansible.ModuleUtils.Whatever.psm1` * Windows modules now support the use of multiple shared module_utils files in the form of Powershell modules (.psm1), via `#Requires -Module Ansible.ModuleUtils.Whatever.psm1`
* Python module argument_spec now supports custom validation logic by accepting a callable as the `type` argument. * Python module argument_spec now supports custom validation logic by accepting a callable as the `type` argument.
* Windows become_method: runas is no longer marked `experimental`
* Windows become_method: runas now works across all authtypes and will auto-elevate under UAC if WinRM user has "Act as part of the operating system" privilege * Windows become_method: runas now works across all authtypes and will auto-elevate under UAC if WinRM user has "Act as part of the operating system" privilege
### Deprecations ### Deprecations

View file

@ -217,10 +217,7 @@ delegation or accessing forbidden system calls like the WUA API. You can use
``become`` with the same user as ``ansible_user`` to bypass these limitations ``become`` with the same user as ``ansible_user`` to bypass these limitations
and run commands that are not normally accessible in a WinRM session. and run commands that are not normally accessible in a WinRM session.
.. note:: While become support was added for Windows starting with Ansible .. note:: Prior to Ansible 2.4, become would only work when ``ansible_winrm_transport`` was
version 2.3, this functionality is still considered experimental and can
change in the future based on issues and limitations that are found. Prior to
Ansible 2.4, become would only work when ``ansible_winrm_transport`` was
set to either ``basic`` or ``credssp``, but since Ansible 2.4 become now works on set to either ``basic`` or ``credssp``, but since Ansible 2.4 become now works on
all transport types. all transport types.

View file

@ -585,8 +585,6 @@ class PlayContext(Base):
elif self.become_method == 'runas': elif self.become_method == 'runas':
# become is handled inside the WinRM connection plugin # become is handled inside the WinRM connection plugin
display.warning("The Windows 'runas' become method is experimental, and may change significantly in future Ansible releases.")
if not self.become_user: if not self.become_user:
raise AnsibleError(("The 'runas' become method requires a username " raise AnsibleError(("The 'runas' become method requires a username "
"(specify with the '--become-user' CLI arg, the 'become_user' keyword, or the 'ansible_become_user' variable)")) "(specify with the '--become-user' CLI arg, the 'become_user' keyword, or the 'ansible_become_user' variable)"))