chore: clear compile warnings; retire SecretManager #346
Owner
- Migrate callers from SecretManager to harmony_config::get_or_prompt
- Lazy-init global ConfigClient from HARMONY_SECRET_NAMESPACE
- Convert remaining Secret derives to Config + #[config(secret)]
- Remove deprecated SecretManager
- Retry::spawn → start; drop unused import; cfg-gate nm_bond_mode
- allow(deprecated) on legacy ApplicationScore examples
- Migrate callers from SecretManager to harmony_config::get_or_prompt
- Lazy-init global ConfigClient from HARMONY_SECRET_NAMESPACE
- Convert remaining Secret derives to Config + #[config(secret)]
- Remove deprecated SecretManager
- Retry::spawn → start; drop unused import; cfg-gate nm_bond_mode
- allow(deprecated) on legacy ApplicationScore examples
johnride
added 1 commit 2026-08-08 22:14:30 +00:00
Some checks failed
Run Check Script / check (pull_request) Failing after 2s
Details
johnride
added 2 commits 2026-08-08 23:55:30 +00:00
All checks were successful
Run Check Script / check (pull_request) Successful in 1m51s
Details
Merge pull request 'chore: clear compile warnings; retire SecretManager' (#346) from chore/clear-compile-warnings into fix/app-deploy-safety
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/clear-compile-warnings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?