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

Standard/reusable CLI flags

Closed
#229 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go, python, typescript
Domain
cli, tooling

Research direction

Start by comparing the CLI boilerplate in the Go, Python, and TypeScript function templates, including flags, environment variables, and defaults. The work is done when the project has an agreed single source of truth and a clear mechanism for propagating standardized options and default changes to functions.

Written by the indexing model from the issue text.

Description

enhancement
What problem are you facing?

Each function author today copies CLI boilerplate (mainly flags, environment variables, and defaults) from the function templates (Go, Python, TS). This leads to eventual inconsistency across functions (env var names drift, each author may decide, e.g. GRPC_MESSAGE_SIZE vs MAX_RECV_MESSAGE_SIZE), some functions miss env tags entirely (e.g. DEBUG), etc.

On top of that, there's no single source of truth and when new standard option is added or a default changes, every function must be updated independently. There is no mechanism to propagate changes.

Standardization of CLI arguments/env variables might become useful for 3rd party tooling (e.g. crossplane-diff) which may need to flag all functions in the composition pipeline at the same time (e.g. programatically raise the max GRPC size in all functions).

Dominant language
Python
Stars
12
Forks
15
Avg merge
1d 12h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

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/function-sdk-python

All issues in crossplane/function-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.