package public names should be fully qualified

[cppforlife]

Feature Request

currently packages have non-qualified public names: cert-manager. instead public names should be following CRD-like naming conventions == fully qualified names.

Current:

apiVersion: package.carvel.dev/v1alpha1
kind: Package
metadata:
  name: fluent-bit.1.7.2-vmware0
spec:
  publicName: fluent-bit
  version: "1.7.2-vmware0"
  # ...

Ideal:

apiVersion: package.carvel.dev/v1alpha1
kind: Package
metadata:
  name: fluent-bit.tce.vmware.com.1.7.2-vmware0
spec:
  publicName: fluent-bit.tce.vmware.com
  version: "1.7.2-vmware0"
  # ...

[rosenhouse]

If package repositories A and B both provide package foo, will this change help a user with disambiguating them?

[jorgemoralespou]

If package repositories A and B both provide package foo, will this change help a user with disambiguating them?

As long as the name is different. This just makes it clear for our conventions.

[cppforlife]

If package repositories A and B both provide package foo, will this change help a user with disambiguating them?

yup. foo.corp.com vs foo.blah.com for example.

[jorgemoralespou]

@joshrosso I'm happy to do this one, but what should be the FQDN to use, as not sure vmware.com should be there, or yes, maybe?

• tce.vmware.com
• tce.org
• tce.io
• tanzucommunityedition

In the true spirit of community should it have the vmware there?

[rosenhouse]

That question reminds me: how does TCE fit in with the GVK naming convention?

[jorgemoralespou]

[REMINDER] Update:

• https://github.com/vmware-tanzu/tce/blob/main/docs/designs/tanzu-addon-management.md
• https://github.com/vmware-tanzu/tce/blob/main/docs/designs/tanzu-addon-packaging.md

Docs and scripts if applicable by the change in this issue

[jorgemoralespou]

/assign @jorgemoralespou