Backward compatibility notes¶
Table of Contents
When installing and using the 0.6.0
and newer releases of YDK-Py
, please note the below issues with backward compatibility.
Installation¶
When installing YDK-Py
, there is a new system requirement which needs to be installed. This is the libydk
library, which is available on the DevHub website for various OS platforms. Please refer to the system requirements for details.
Windows Support¶
From release 0.6.0
onwards, YDK no longer is supported on the Windows platform. We hope to add back support for this platform in the future.
API Changes¶
NetconfServiceProvider
no longer has theclose()
method. There is no need to explicitly close the provider as it will be automatically cleaned up when the object goes out of scope.YFilter
has replaced the functionality of theREAD
andDELETE
objects- When using YDK’s Logging, the suggested level to be used is
INFO
- The type names of
enumerations
andidentities
no longer haveEnum
orIdentity
in their names. For example, the identityInterfaceTypeIdentity
inydk.models.ietf.ietf_interfaces
is now renamed to justInterfaceType
. - The
is_config()
method is no longer available for the YDK model APIs. This may be added back in a future release. - For
CRUDService
and other services, using a child container or list, which is not the top-level node in a yang model is no longer supported. For example:
1 2 3 4 5 6 | from ydk.models.cisco_ios_xe import Cisco_IOS_XE_bgp_oper as bgp_oper
# connect to provider etc ...
neighbors = bgp_oper.BgpStateData.Neighbors()
crud.read(provider, neighbors)
|
now has to be changed to:
1 2 3 4 5 6 | from ydk.models.cisco_ios_xe import Cisco_IOS_XE_bgp_oper as bgp_oper
# connect to provider etc ...
bgp_state = bgp_oper.BgpStateData()
crud.read(provider, bgp_state)
|