Skip to content

feat: extensible bootstrap command - #4317

Draft
reubenmiller wants to merge 5 commits into
thin-edge:mainfrom
reubenmiller:feat-bootstrap-command
Draft

reubenmiller wants to merge 5 commits into
thin-edge:mainfrom
reubenmiller:feat-bootstrap-command

Conversation

@reubenmiller

@reubenmiller reubenmiller commented Sep 1, 2026 •

Copy link
Copy Markdown
Contributor

Proposed changes

New extensible bootstrap command to allow easier configuration of thin-edge.io.

Goal

  • Make it easier for users to connect thin-edge.io to a cloud (configure, connect and verify)
  • Custom mappers should be treated as first class
  • Allow extending the bootstrap process at various phases

Some feature include:

  • Guided tedge bootstrap command that guides users through the entire setup from settings, to connecting the mapper to the cloud (along with verification)
  • Users / package maintainers can add custom hooks that are called during different phases of bootstrapping of a cloud (e.g. c8y, az, c8y)
  • Allow custom cloud bootstrap descriptors which allow users to custom existing mappers, or create new ones to support configuring new cloud mappers which each have their own specific onboarding requirements (e.g. thingsboard allows onboarding via a token, certificate, or provisioning credentials)
  • Support Cumulocity username/password device credentials request or pre-registered credentials

TODO

  • User documentation
  • Cleanup design doc (or remove it if the user documentation is sufficient)

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue


Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s. You can activate automatic signing by running just prepare-dev once)
  • I ran just format as mentioned in CODING_GUIDELINES
  • I used just check as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@reubenmiller reubenmiller added the theme:cli Theme: cli related topics label Sep 1, 2026
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass % ⏱️ Duration
1016 0 8 1016 100 3h19m15.655706999s

reubenmiller and others added 5 commits September 11, 2026 10:04
Signed-off-by: reubenmiller <reuben.d.miller@gmail.com>
Signed-off-by: reubenmiller <reuben.d.miller@gmail.com>
Signed-off-by: reubenmiller <reuben.d.miller@gmail.com>
Signed-off-by: reubenmiller <reuben.d.miller@gmail.com>
The user documentation is now the reference for the hook contract,
the descriptor format and the command usage, so the design record
keeps only the problem, the decisions, the rejected alternatives
and the open questions, and points at the docs for the rest.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: reubenmiller <reuben.d.miller@gmail.com>

This branch had an error being deployed

1 failed and 1 inactive (outdated) deployments
Test Pull Request — f205f06d Deployed Sep 11, 2026 by reubenmiller via Approve #8585
Test Auto — a4f79eb0 Deployed Sep 1, 2026 by reubenmiller via Test x86_64 #8510
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

theme:cli Theme: cli related topics

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant