Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CTA CTA
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 139
    • Issues 139
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

GitLab Runners cleaning campaign ongoing (ETA 2nd October 2023). Check https://cern.ch/otg0078219 for further information.

  • ctacta
  • CTACTA
  • Issues
  • #341
Closed
Open
Issue created Mar 24, 2023 by Volodymyr Yurchenko@vyurchenOwner

Normalize usage of encryptionKeyName

When tape is encrypted, we store a name of encryption key (e.g., r_validation_v1) to look up for encryption key value.

When tape is unencrypted the default value is different in several places:

  • in the catalogue encryptionKeyName is stored as null
  • cta-admin --json ta ls displays "-"
  • XrdCtaTapeLs sets "-"
  • in protobuf TapeLsItem it is optional string type
  • cta-get-encryption-key expects "-"

We should decide which default value we will use and apply it to all sources.

Assignee
Assign to
Time tracking