Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support connection secrets in `crossplane beta render`

Open
#73 21 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #5985 by @avarei — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start at the crossplane beta render entry point and trace its Function pipeline inputs and outputs. Define how mocked observed composed-resource connection details are represented and how XR connection details are surfaced, then verify that both workflows work with the chosen input/output format.

Written by the indexing model from the issue text.

Description

enhancement
What problem are you facing?

Compositions can be used to produce XR connection secrets (aka connection details), typically by deriving them somehow from composed resources. crossplane beta render doesn't currently support surfacing the XR connection details returned by the Function pipeline. It also doesn't support passing in mocked connection details for composed resources (which are often the source from which XR connection details are derived).

How could Crossplane help solve your problem?

We could support:

  • Passing in mocked "observed" composed resource connection details.
  • Printing out XR connection details.

One thing we'll need to consider is the input/output format. Would Kubernetes Secrets suffice? Crossplane has alpha support for other secret stores (e.g. HashiCorp Vault) but maybe Secrets are a good enough general representation.

Dominant language
Go
Stars
19
Forks
31
Avg merge
2d 15h
Merged PRs (30d)
53

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from crossplane/cli

All issues in crossplane/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.