Omniverse Wrapp Change Log#

1.1.2#

  • Updates for security vulnerabilities

    • Update ClientLibrary to 2.54.0.

1.1.1#

  • Updates for security vulnerabilities

    • Update Python to 3.10.15+nv1.

    • Update aiohttp to 3.10.10.

    • Update ClientLibrary to 2.53.2.

1.1.0#

  • On Windows, before running wrapp you need to install the Microsoft runtime in case it is not already installed. Download and install from https://aka.ms/vs/17/release/vc_redist.x64.exe.

  • Allow using S3 as target for install, import, and create commands. S3 can be addressed both with global s3:// style URLs and https:// style links pointing to amazonaws.com.

  • OMPE-15135: freeze would not create local file system folders when copying from S3

  • Introduce progress report flag and additional options for number of tagging and file transfer jobs for create, install, mirror, freeze and apply-patch.

API Changes:#

  • The “get” API function used to download a file to the local disk is now accepting the optional parameters “context” and “scheduler”, like the other API functions.

  • The credentials used to sign in to S3 can be set using WRAPP_AWS_ACCESS_KEY_ID and WRAPP_AWS_SECRET_ACCESS_KEY, the endpoint can be set with WRAPP_S3_ENDPOINT.

    • If the variables are not set, boto3 tries to locate the credential in the usual way.

  • The API initialize function is now documented to possibly raise a RuntimeError when initialization fails.

    • Before it might have thrown any exception.

1.0.1#

  • Update ClientLibrary to 2.49.0 release, closing security vulnerabilities

  • Updated to use Python 3.10.14+nv1 instead of 3.10.13+nv3

  • Linux-binaries built on Ubuntu 20.04 LTS instead of CentOS 7, which is EOL

  • New documentation

1.0.0#

  • Initial Omniverse Nucleus WRAPP release.

On this page