Skip to content

feat(config): add sensitive attribute metadata to configuration params#4775

Draft
PranjalC100 wants to merge 1 commit into
masterfrom
cfg-sensitive-metadata
Draft

feat(config): add sensitive attribute metadata to configuration params#4775
PranjalC100 wants to merge 1 commit into
masterfrom
cfg-sensitive-metadata

Conversation

@PranjalC100

Copy link
Copy Markdown
Member

Description

This PR introduces the sensitive property for all GCSFuse configuration parameters. The configuration generator (tools/config-gen) is updated to parse and validate that the sensitive attribute is explicitly set (true or false) for every parameter defined in cfg/params.yaml.

The following 11 parameters have been classified as sensitive (sensitive: true):

  • cache-dir (Flag: --cache-dir)
  • file-system.kernel-params-file (Flag: --kernel-params-file)
  • file-system.temp-dir (Flag: --temp-dir)
  • gcs-auth.key-file (Flag: --key-file)
  • gcs-auth.token-url (Flag: --token-url)
  • gcs-connection.custom-endpoint (Flag: --custom-endpoint)
  • gcs-connection.experimental-local-socket-address (Flag: --experimental-local-socket-address)
  • logging.file-path (Flag: --log-file)
  • logging.wire-log (Flag: --wire-log)
  • only-dir (Flag: --only-dir)
  • workload-insight.output-file (Flag: --workload-insight-output-file)

All other parameters are explicitly marked as sensitive: false.

Link to the issue in case of a bug fix.

N/A

Testing details

  1. Manual - Verified that running go generate ./... succeeds and generated files remain correct. Audited all parameters in cfg/params.yaml to ensure no sensitive path, socket, or token configurations are missed.
  2. Unit tests - go test ./cfg/... (Passed), go test ./tools/config-gen/... (Passed)
  3. Integration tests - N/A

Any backward incompatible change? If so, please explain.

N/A

@codecov

codecov Bot commented Jun 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.69%. Comparing base (d47010c) to head (b81fd43).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4775      +/-   ##
==========================================
+ Coverage   83.67%   83.69%   +0.01%     
==========================================
  Files         168      168              
  Lines       20784    20784              
==========================================
+ Hits        17392    17396       +4     
+ Misses       2742     2739       -3     
+ Partials      650      649       -1     
Flag Coverage Δ
unittests 83.69% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@PranjalC100 PranjalC100 added the execute-integration-tests Run only integration tests label Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

execute-integration-tests Run only integration tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant