[Bug 2077382] Re: [SRU] support additional parametes on deploy()

[Alan Baghumian]

** Description changed:

- This is a SRU bug report for this feature that has already been merged
- upstream (1).
+ [Impact]
  
- This implements support for ephemeral_deploy as well as enable_hw_sync
- on deploy().
+ * This SRU is not addressing an existing problem but adds support for
+ two additional optional parameters being ephemeral_deploy and
+ enable_hw_sync on deploy(). For more details please see (1).
+ 
+ 
+ [ Where problems could occur ]
+ 
+ * Due to the nature of the change and the additional parameters being
+ optional we are not expecting any adverse effect on existing integration
+ using python-libmaas.
  
  
  (1) https://github.com/canonical/python-libmaas/issues/300

** Description changed:

- [Impact]
+ [ Impact ]
  
  * This SRU is not addressing an existing problem but adds support for
  two additional optional parameters being ephemeral_deploy and
  enable_hw_sync on deploy(). For more details please see (1).
- 
  
  [ Where problems could occur ]
  
  * Due to the nature of the change and the additional parameters being
  optional we are not expecting any adverse effect on existing integration
  using python-libmaas.
  
- 
  (1) https://github.com/canonical/python-libmaas/issues/300

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-libmaas in Ubuntu.
https://bugs.launchpad.net/bugs/2077382

Title:
  [SRU] support additional parametes on deploy()

Status in python-libmaas package in Ubuntu:
  In Progress
Status in python-libmaas source package in Jammy:
  In Progress
Status in python-libmaas source package in Noble:
  In Progress
Status in python-libmaas source package in Oracular:
  In Progress

Bug description:
  [ Impact ]

  * This SRU is not addressing an existing problem but adds support for
  two additional optional parameters being ephemeral_deploy and
  enable_hw_sync on deploy(). For more details please see (1).

  [ Where problems could occur ]

  * Due to the nature of the change and the additional parameters being
  optional we are not expecting any adverse effect on existing
  integration using python-libmaas.

  (1) https://github.com/canonical/python-libmaas/issues/300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+subscriptions