<commit_before>apiVersion: v1
kind: Secret
metadata:
  name: ceph-secret
data:
  key: <KEY>
<commit_msg>added comment to clarify that the already-base64-encoded Ceph key must be base64-encoded again when using Kubernetes Secrets, or else use 'stringData' inplace of 'data'<commit_after>apiVersion: v1
kind: Secret
metadata:
  name: ceph-secret
data:
  key: <KEY>  # the base64-encoded string of the already-base64-encoded key `ceph auth get-key` outputs

{'fraction_non_alphanumeric': 0.08590308370044053, 'fraction_numerical': 0.022026431718061675, 'mean_word_length': 5.148648648648648, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6945660', 'n_tokens_mistral': 151, 'n_tokens_neox': 144, 'n_words': 54}