Skip to content
This repository was archived by the owner on May 18, 2026. It is now read-only.
This repository was archived by the owner on May 18, 2026. It is now read-only.

tail seems to fail if workload name includes . char #663

@heyjcollins

Description

@heyjcollins
  • I reviewed open and closed Github issues that may be related to my problem.
  • I am reporting a bug that others will be able to reproduce.

Describe the bug

tanzu apps workload tail throws an error if there are periods ('.') in the workload name

$ tanzu apps workload tail -n official ucp.ucp-package.lever-v2 --timestamp --since 1h --verbose 10
Usage:
  tanzu apps workload tail <name> [flags]

Examples:
  tanzu apps workload tail my-workload
tanzu apps workload tail my-workload --since 1h

Flags:
      --component name   workload component name (e.g. build)
  -h, --help             help for tail
  -n, --namespace name   kubernetes namespace (defaulted from kube config)
      --since duration   time duration to start reading logs from (default 1m0s)
  -t, --timestamp        print timestamp for each log line

Global Flags:
      --context name      name of the kubeconfig context to use (default is current-context defined by kubeconfig)
      --kubeconfig file   kubeconfig file (default is $HOME/.kube/config)
      --no-color          deactivate color, bold, and emoji output
  -v, --verbose int32     number for the log level verbosity (default 1)

Error: name: Invalid value: "ucp.ucp-package.lever-v2"

NOTE: Let's keep this validation in place for tanzu apps workload create/apply... but remove it for all other tanzu apps workload... sub-commands.

Expected behavior

The tail command should...tail the logs successfully

Steps to Reproduce

  1. use kubectl to create a workload with a period in the name, e.g. workload.name
  2. run tanzu apps workload tail workload.name --timestamp --since 1h

Screenshots

If applicable, add screenshots to help explain your proble

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions