Skip to content

RUN-4336: Update encryptable-properties docs for AES-256-GCM encryption#1801

Closed
Jesus-Osuna-M wants to merge 18 commits into5.20.1from
docs/update-encryptable-properties-aes-gcm
Closed

RUN-4336: Update encryptable-properties docs for AES-256-GCM encryption#1801
Jesus-Osuna-M wants to merge 18 commits into5.20.1from
docs/update-encryptable-properties-aes-gcm

Conversation

@Jesus-Osuna-M
Copy link
Copy Markdown
Contributor

Summary

  • Updates the encryptable-properties documentation to reflect the migration from Jasypt to AES-256-GCM in Rundeck 6.0
  • Removes references to "Jasypt encryption library" (Jasypt has been eliminated)
  • Adds upgrade note clarifying that existing ENC() values are automatically detected and decrypted without changes
  • Clarifies that algorithm/provider/iterations config now only affects decryption of legacy values
  • Adds "Re-encrypting Legacy Values" section for voluntary migration

Related

Test plan

  • Verify docs build without errors
  • Review rendered page for formatting

Made with Cursor

brmdias and others added 16 commits April 15, 2026 12:18
Clarified that AI-Generated Runbooks are only available in Runbook Automation SaaS and not in the Self-Hosted product.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Part of the AI sprint: establish a shared .claude/ directory consumed by
both Claude Code and Cursor so the repository is AI-ready.

- .claude/docs/: canonical reference (writing style, local dev,
  infrastructure, PR feed, DocSearch filters) in kebab-case
- .claude/skills/: starter workflow skills for the two automated
  pipelines (write-release-notes, generate-pr-feed)
- .claude/rules/: auto-loaded rule enforcing release-notes PR discipline
- .claude/README.md + CONTRIBUTING.md: structure and extension guide
- CLAUDE.md (repo root): conventions index; AGENTS.md symlinks to it
- .cursor/ symlinks docs, rules, skills into .claude/ so both tools
  draw from a single source of truth
- dev-docs/DOCSEARCH_FILTERS_README.md and PR-FEED-README.md: now
  symlinks into .claude/docs/ (external paths preserved)
- .github/copilot-instructions.md slimmed to a pointer into CLAUDE.md
  and .claude/docs/writing-style.md to prevent drift

Made-with: Cursor
- docsearch-filters.md: replace outdated "import/place in layout"
  troubleshooting advice with pointers to the actual auto-injection
  logic in docs/.vuepress/client.ts (#docsearch-container)
- pr-feed.md: remove git push from the sample commit block;
  add explicit reminder of the "no push without instruction" rule
- write-release-notes SKILL: split Phase 2 into "create tag" and
  "push tag" so the push step requires explicit confirmation;
  add Phase 6 to gate the final push
- settings.json:
  - drop Read(~/.cache/pagerduty/**) now that the manifest
    pre-task block has been removed
  - broaden Write/Edit docs globs to docs/**/*.md and
    docs/.vuepress/** so the agent can actually edit
    manual/administration/api/developer content
  - add .docsearch/config.json and .claude/** for legitimate
    maintenance writes
- local-development.md, infrastructure.md: promote top heading to
  H1 for consistency with the other .claude/docs/* files
- infrastructure.md: correct check-milestone.yml trigger description
  to reflect pull_request_target with opened/synchronize/reopened/
  milestoned/demilestoned on 4.0.x

Made-with: Cursor
Factual corrections verified against docs/.vuepress/notes.mjs,
docs/.vuepress/pr-feed.mjs, and package.json:

- .claude/README.md: correct symlink destination wording to
  ".claude/docs/" (not "docs/") so the canonical source is clear
- .claude/docs/pr-feed.md:
  - remove invalid "--owner=... --repo=..." example
  - correct --include-section default column: the script has no
    default; "Release Notes" is supplied by the npm run pr-feed
    script in package.json
- CLAUDE.md, .claude/skills/write-release-notes/SKILL.md,
  .claude/rules/release-notes-pr.md: remove ".docsearch/config.json"
  from the release-notes side-effect staging list since notes.mjs
  no longer updates it (updateDocsearchVersion is commented out).
  Add a "run git status to catch any other modified files"
  instruction so guidance stays accurate if the script evolves.

Made-with: Cursor
Fix typo in script file step description
Agent-Logs-Url: https://github.com/rundeck/docs/sessions/6960f553-1606-4f65-95c1-0d0c5d33e5c7

Co-authored-by: jtobard <2894508+jtobard@users.noreply.github.com>
…iption

RUN-2581 Fix node filter description wording
Update availability information for AI-Generated Runbooks
Document the JVM system properties available to tune Runner capacity
when users hit "Runner did not deliver reports in the configured
timeout period" errors under heavy load.

Covers:
- Operation concurrency (runner.operations.maxRunning)
- Report delivery batching (sendRate, sendBatchSize) with a warning
  that changing these puts additional load on the server and the
  defaults are recommended
- Micronaut HTTP client pool and timeouts

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
[RUN-4403] Scaffolds AI for Claude Code and Cursor with sdlc-workflow skill
Add performance tuning section for high-throughput Runners
Reflects the migration from Jasypt to AES-256-GCM in Rundeck 6.0:
- Remove references to "Jasypt encryption library"
- Add upgrade note about automatic backward compatibility
- Clarify that algorithm config only affects legacy decryption
- Add section on re-encrypting legacy values

Co-authored-by: Cursor <cursoragent@cursor.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the encryptable properties documentation to reflect the Rundeck 6.0 migration from legacy Jasypt-based encryption to AES-256-GCM, including upgrade guidance and a voluntary re-encryption path for legacy ENC(...) values.

Changes:

  • Replaces Jasypt-library wording with AES-256-GCM terminology and updates the example encrypted output format.
  • Adds an upgrade note explaining automatic detection/decryption of legacy ENC() values.
  • Reframes “Advanced Usage” as legacy decryption configuration and adds a “Re-encrypting Legacy Values” section.

Comment thread docs/administration/configuration/encryptable-properties.md
Comment thread docs/administration/configuration/encryptable-properties.md
Comment thread docs/administration/configuration/encryptable-properties.md
Comment thread docs/administration/configuration/encryptable-properties.md Outdated
Comment thread docs/administration/configuration/encryptable-properties.md Outdated
- Add info callout explaining 'Jasypt' is a legacy CLI name kept for compat
- Add language tag (text) to interactive prompt code block
- Fix Java -D property ordering (must come before -jar)
- Add explanation of Encrypter Config name linkage
- Add info callout in re-encryption section about legacy provider name

Co-authored-by: Cursor <cursoragent@cursor.com>
@fdevans fdevans changed the base branch from 4.0.x to grails7-upgrade May 5, 2026 15:46
- bundled-plugins.md: Rewrite plugin section with new/upgrade examples,
  clarify algorithm/provider only needed for legacy decryption
- storage-facility.md: Update section title, examples, remove algorithm
  options table (no longer configurable)
- secrets-overview.md: Update plugin link and example config
- full-list.md: Update plugin name and link
- storage-converter-plugins.md: Update plugin description
- migrate-to-mysql.md: Update link
- azure-vault.md: Update converter type reference

Co-authored-by: Cursor <cursoragent@cursor.com>
@Jesus-Osuna-M Jesus-Osuna-M changed the base branch from grails7-upgrade to 4.0.x May 5, 2026 16:17
@Jesus-Osuna-M Jesus-Osuna-M changed the base branch from 4.0.x to 5.20.1 May 5, 2026 16:17
@Jesus-Osuna-M Jesus-Osuna-M force-pushed the docs/update-encryptable-properties-aes-gcm branch from c24192f to 96dec1b Compare May 5, 2026 16:29
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.

8 participants