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

using Composition Functions may extra auto-require function at end of pipeline

Open
#797 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
hugo, python
Domain
documentation

Research direction

Start with the “Test a composition that uses functions” section at the linked documentation URL, then review the issue’s example involving a Python function and function-auto-ready v0.2.1. Update the page with a clear explanation of when an extra auto-readiness function may be needed and what remedy to use, so readers can understand why a composition may not reach complete.

Written by the indexing model from the issue text.

Description

bug
URL

What's Wrong?

When using composition functions in a composition there may be a need to end the pipeline with the extra auto-readiness function
https://marketplace.upbound.io/functions/crossplane-contrib/function-auto-ready/v0.2.1

This seems to be the case when using a custom function to add resources.

For instance I wrote a python function that adds resources but could not reach complete even though it added a number of composite resources as resources that reached ready in my composition.

There is no explanation anywhere as to why that is the case or what could be done to remedy it.

adding a blurb that this is possible when using functions

Dominant language
SCSS
Stars
60
Forks
163
Avg merge
1d 5h
Merged PRs (30d)
9

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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/docs

All issues in crossplane/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.