Visitar URL original
docs(user-secrets-api): fix facts found in review, add open questions by myasnikovdaniil · Pull Request #121 · cozystack/community · GitHub
Skip to content

docs(user-secrets-api): fix facts found in review, add open questions - #121

Draft
myasnikovdaniil wants to merge 1 commit into
mainfrom
design-proposal/user-secrets-api-amendments
Draft

myasnikovdaniil wants to merge 1 commit into
mainfrom
design-proposal/user-secrets-api-amendments

Conversation

@myasnikovdaniil

Copy link
Copy Markdown
Contributor

Reviewing cozystack/cozystack#4920, cozystack/cozystack#4921 and cozystack/cozystack#4922 showed statements in the proposal that are wrong or incomplete, so this PR fixes them and adds the questions that came out of it. Nothing is decided here.

Fixed

  • the lineage webhook keeps an explicit "false" on create only, the cacert controller hands a CA projection back to it after a selector change (Context, Upgrade, Security, Testing, Rollout)
  • helm-controller waits for the Jobs of a release and the platform HelmRelease doesn't set disableWaitForJobs, so the post-switch Job counts against the upgrade timeout
  • feat(postgres,mariadb)!: drop plaintext user passwords cozystack#4078 only warns about users.*.password, it doesn't drop the value
  • a create on a name that a live application holds leaves its Secrets alone, a dry run writes nothing, migrated postgres passwords go through SASLprep
  • Testing said users.app still adopts the role CNPG bootstraps while the Failure section says it is refused, Testing was wrong and says refused now

Open questions

  1. what a release with users.app does at the conversion, it is used in production (fix(postgres): keep users.app's password across pod restarts cozystack#4984)
  2. how the post-switch Job runs
  3. when the pre-upgrade hook runs
  4. which migration errors skip a release
  5. drop or warn for a password under users

No decision record, these are corrections of fact and open questions, nothing is settled yet.

Before review

  • If this revises a merged design proposal: it adds a decision record under that proposal's decisions/ directory, or says above why none is needed.

DCO

  • Commits are signed off (git commit --signoff).

Correct what the review of the implementation PRs showed the proposal
got wrong or left out:

- the lineage webhook re-admits a CA projection after a selector
  change, so an explicit "false" is kept on create only
- helm-controller waits for the Jobs of a release, so the post-switch
  Job does not escape the upgrade timeout
- cozystack/cozystack#4078 only warns about users.*.password
- a create on a taken name leaves the live Secrets alone
- a dry run writes nothing
- migrated PostgreSQL passwords go through SASLprep
- Testing says users.app is refused, as the Failure section does

Add the questions the review raised: users.app on existing releases,
how the post-switch Job runs, when the pre-upgrade hook runs, which
migration errors skip a release, and whether a password under users
is dropped or only warned about.

Assisted-By: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
@coderabbitai

coderabbitai Bot commented Oct 29, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant