XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Major Major
    • 3.3.0.GA
    • 3.3.0.GA
    • None
    • None
    • False
    • None
    • False
    • Release Notes
    • Hide
      = Updated Universal Developer Image

      In {prod-short} {prod-ver}, the Universal Developer Image (UDI) is updated as follows:

      * Improved Python 3.9 tooling support:
      ** `jq` (JSON parsing) and `yq` (YAML parsing) have been included.
      ** `pytest` has been added to the path (along with `pylint` and `pip`) for easier use.
      * The `kamel` binary has been removed.

      [TIP]
      ====
      To include other tools or runtimes, an administrator can extend, fork, or replace the UDI image with one that includes the tools appropriate for your organization and your users' needs. That replacement image can then be referenced in the `CheCluster` custom resource, so that users can use the custom image in their devfiles. This will ensure that the tools and runtimes they need are persistent and do not need to be installed on each workspace startup.

      Users can also develop their own UDI image(s) and refer to them from their devfiles. This requires publishing the image to a registry that is accessible from their organization's cluster. However, this approach is less centralized and standardized, and may not scale or perform as well.
      ====
      Show
      = Updated Universal Developer Image In {prod-short} {prod-ver}, the Universal Developer Image (UDI) is updated as follows: * Improved Python 3.9 tooling support: ** `jq` (JSON parsing) and `yq` (YAML parsing) have been included. ** `pytest` has been added to the path (along with `pylint` and `pip`) for easier use. * The `kamel` binary has been removed. [TIP] ==== To include other tools or runtimes, an administrator can extend, fork, or replace the UDI image with one that includes the tools appropriate for your organization and your users' needs. That replacement image can then be referenced in the `CheCluster` custom resource, so that users can use the custom image in their devfiles. This will ensure that the tools and runtimes they need are persistent and do not need to be installed on each workspace startup. Users can also develop their own UDI image(s) and refer to them from their devfiles. This requires publishing the image to a registry that is accessible from their organization's cluster. However, this approach is less centralized and standardized, and may not scale or perform as well. ====
    • Enhancement
    • Done

      This is a by-release Jira issue for grouping all language version upgrades and minor changes.

      1. Clone it for every next release.
      2. Add all language changes into one list inside one release note.
      3. Link the Jira issues where the language updates are mentioned to this issue as 'documented by'.

       

              nickboldt Nick Boldt
              jvrbkova@redhat.com Jana Vrbkova
              Jana Vrbkova Jana Vrbkova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: