Files
cozystack/.gitignore
T
Andrey Kolkov 9673af6aca fix(kafka): guard short backup drains and settle example teardown
- Short-drain guard: kafka-console-consumer exits 0 after a timed-out
  short read, so a truncated drain was tarred and reported Succeeded.
  Compare the drained line count against end-begin per partition and
  fail the backup on any shortfall, making the README's "fails closed"
  promise real for compacted/transactional topics.
- Settling teardown: cleanup.sh returned before the Kafka apps and
  Bucket had uninstalled and could not report failure, letting the
  neighbouring chainsaw/kafka Test contend on PVC reclaim. Add a
  wait_deleted helper and a teardown_rc gate that waits for the heavy
  objects and exits non-zero when the teardown does not settle.
- Fully qualify the ambiguous delete kinds (backup/bucket/backupclass/
  restorejob/backupjob) so a bare shortcut cannot target a foreign group
  and silently leave the Cozystack artifact behind.
- Default KAFKA_IMAGE from the running operator (newest STRIMZI_KAFKA_
  IMAGES entry), falling back to the literal only when the operator
  cannot be read; drop the duplicate resolution note.
- Make the strategy and throwaway CLI Pods restricted-clean
  (runAsNonRoot + JSON-patch securityContext on the CLI Pods).
- gitignore .source-dump.txt; replace the deprecated "small" preset with
  c1.small; capture the to-copy cluster in the e2e catch; document the
  all-topics risk; de-enumerate the decaying suite-list comments.

Signed-off-by: Andrey Kolkov <andrey.kolkov@aenix.io>
Assisted-by: LLM
2026-09-23 17:44:17 +04:00

154 lines
3.9 KiB
Plaintext

_out
_repos
.git
.idea
.vscode
# Go binaries built straight into the repository root.
#
# `go build ./cmd/<name>` (without -o) drops the executable in the working
# directory under the package name, so every package under cmd/ has a
# root-level binary waiting to happen — each ~80 MB, and nothing else here
# matched them, leaving `git add .` one keystroke from committing one.
/api-gate
/backup-controller
/backupstrategy-controller
/check-readiness
/cozypkg
/cozystack-api
/cozystack-controller
/cozystack-operator
/flux-plunger
/flux-shard-operator
/kubeovn-plunger
/lineage-controller-webhook
/securitygroup-controller
# User-specific stuff
.idea/**/workspace.xml
.idea/**/tasks.xml
.idea/**/usage.statistics.xml
.idea/**/dictionaries
.idea/**/shelf
# AWS User-specific
.idea/**/aws.xml
# Generated files
.idea/**/contentModel.xml
# Sensitive or high-churn files
.idea/**/dataSources/
.idea/**/dataSources.ids
.idea/**/dataSources.local.xml
.idea/**/sqlDataSources.xml
.idea/**/dynamic.xml
.idea/**/uiDesigner.xml
.idea/**/dbnavigator.xml
# Gradle
.idea/**/gradle.xml
.idea/**/libraries
# Gradle and Maven with auto-import
# When using Gradle or Maven with auto-import, you should exclude module files,
# since they will be recreated, and may cause churn. Uncomment if using
# auto-import.
# .idea/artifacts
# .idea/compiler.xml
# .idea/jarRepositories.xml
# .idea/modules.xml
# .idea/*.iml
# .idea/modules
# *.iml
# *.ipr
# CMake
cmake-build-*/
# Mongo Explorer plugin
.idea/**/mongoSettings.xml
# File-based project format
*.iws
# IntelliJ
out/
# mpeltonen/sbt-idea plugin
.idea_modules/
# JIRA plugin
atlassian-ide-plugin.xml
# Cursive Clojure plugin
.idea/replstate.xml
# Crashlytics plugin (for Android Studio and IntelliJ)
com_crashlytics_export_strings.xml
crashlytics.properties
crashlytics-build.properties
fabric.properties
# Editor-based Rest Client
.idea/httpRequests
# Android studio 3.1+ serialized cache file
.idea/caches/build_file_checksums.ser
.DS_Store
**/.DS_Store
tmp/
# build revision marker (generated by make image-packages)
packages/core/platform/.build-revision
# Agent tooling. The md-no-hardwrap hook and its registration are shared with
# every contributor, so they are tracked by name; personal agent state (local
# settings overrides, worktrees, session data) stays out of git. Put personal
# overrides in .claude/settings.local.json -- .claude/settings.json is tracked
# and git will overwrite it on pull.
.claude/*
!.claude/hooks/
.claude/hooks/*
!.claude/hooks/md-no-hardwrap.py
!.claude/settings.json
# Credentials and runtime state minted by the backup/restore demo scripts
# under examples/backups/*/. Files are written by 00-helpers.sh +
# 02-create-bucket.sh + 04-create-backupjob.sh; cleanup.sh deletes them
# on teardown. Keep them out of git so a tenant who runs the demo and
# then `git add .` does not accidentally commit S3 keys.
examples/backups/*/.bucket-info.env
examples/backups/*/.sentinel.env
examples/backups/*/.backup-name.env
examples/backups/*/.source-dump.txt
packages/core/platform/images/migrations/etcd-operator-crds/
# CI scratch: promote-rc.yaml checks the dispatch ref here so release tooling
# (validator, agent instructions) is current even when the checked-out rc tag
# predates it. Never committed.
.release-tooling
# Machine credentials and boot artifacts hack/e2e-prepare-cluster.bats writes
# to the repository root when the e2e sandbox is brought up outside CI: the
# Talos secrets bundle and rendered machine configs, the kubeconfigs, the boot
# image and the per-VM directories. secrets.yaml holds the cluster's private
# keys, and before this block nothing here matched any of them -- leaving
# `git add -A` in a tree that once ran the bringup one keystroke from
# committing a credentials bundle.
/secrets.yaml
/talosconfig
/kubeconfig
/tenantkubeconfig*
/controlplane.yaml
/worker.yaml
/patch.yaml
/patch-controlplane.yaml
/nocloud-amd64.raw
/nocloud-amd64.raw.xz
/srv1/
/srv2/
/srv3/