Skip to content

Adopt managed secret connection variables across the catalog - #303

Draft
willdavsmith wants to merge 1 commit into
willdavsmith-secret-connection-env-varsfrom
willdavsmith-phase-2-catalog-adoption
Draft

Adopt managed secret connection variables across the catalog#303
willdavsmith wants to merge 1 commit into
willdavsmith-secret-connection-env-varsfrom
willdavsmith-phase-2-catalog-adoption

Conversation

@willdavsmith

@willdavsmith willdavsmith commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Summary

  • update catalog resource descriptions and examples so one producer connection documents ordinary properties alongside managed secret-backed CONNECTION_* variables
  • retain properties.secrets.name only for explicitly authored Kubernetes secretKeyRef variables
  • preserve RabbitMQ guidance for the conditional user-supplied Secret path

Scope

This is catalog adoption only. It does not change Container Recipe runtime code, Recipe output keys, schema shapes, ACI behavior, or runtime tests.

Dependencies

Validation

  • exact 21-file allowlist and excluded-path checks
  • YAML parsing with yq
  • Bicep formatting with the Radius-bundled Bicep compiler
  • Markdown lint
  • spelling
  • git diff --check

Direct Bicep compilation was unavailable locally because the standalone compiler does not have the Radius extension registered.

Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@willdavsmith willdavsmith changed the title Phase 2: Adopt managed secret connection variables across the catalog Adopt managed secret connection variables across the catalog Aug 20, 2026
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