You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Carvel imgpkg tool is used by Build Tooling for Integrations to build and publish both controllers and Tanzu CLI plugins.
The imgpkg URL for package-tools (for building and publishing controllers) is stored in a config file located in package-tools/cmd/config/carvel-tools-config.yaml:
Build Tooling for Integrations should get the Carvel imgpkg version and URL using a common pathway or a common place.
Expected Outcome:
The URL and version should be configurable by the end user.
Enable end users to download the Carvel imgpkg binary from a private, internal location, and not from the public internet.
The URL and versions used by package-tools and building/publishing Tanzu CLI plugins should by default be the same. According to @yharish991, divergent imgpkg versions may cause problems.
The text was updated successfully, but these errors were encountered:
Background Information
Currently, the Carvel imgpkg tool is used by Build Tooling for Integrations to build and publish both controllers and Tanzu CLI plugins.
The imgpkg URL for package-tools (for building and publishing controllers) is stored in a config file located in package-tools/cmd/config/carvel-tools-config.yaml:
The imgpkg URL for plugins is stored in templates/Dockerfile:
At one point (code was not merged), the imgpkg version for plugins was retrieved via a config file that was not always reachable:
This issue was created in response to a few feedback comments from @sathyanarays and @avi-08 for a pull request:
Feature Description:
Build Tooling for Integrations should get the Carvel imgpkg version and URL using a common pathway or a common place.
Expected Outcome:
The text was updated successfully, but these errors were encountered: