Skip to content

allow overriding of deploy params by a vendor - #643

Draft
evgeni wants to merge 1 commit into
masterfrom
vendor-override
Draft

allow overriding of deploy params by a vendor#643
evgeni wants to merge 1 commit into
masterfrom
vendor-override

Conversation

@evgeni

@evgeni evgeni commented Jul 10, 2026

Copy link
Copy Markdown
Member

Why are you introducing these changes? (Problem description, related links)

Vendors might want to override our CLI definition

What are the changes introduced in this pull request?

  • Make it so

How to test this pull request

Steps to reproduce:

Checklist

  • Tests added/updated (if applicable)
  • Documentation updated (if applicable)

Comment thread src/playbooks/_vendor_override/metadata.obsah.yaml Outdated
flavor:
help: Base flavor to use in this deployment.
choices:
- satellite

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Obviously, this file should not be shipped like this in foremanctl, but be provided by a vendor-branding-package

@evgeni
evgeni force-pushed the vendor-override branch 2 times, most recently from 2b38df4 to 271a777 Compare July 31, 2026 10:48
@ehelms

ehelms commented Aug 5, 2026

Copy link
Copy Markdown
Member

I was thinking this should get merged (the parts that make sense to) and then CI for #726 should create the vendor file. This would then reflect the model we expect and test this override method?

@evgeni evgeni mentioned this pull request Aug 6, 2026
2 tasks
@evgeni

evgeni commented Aug 11, 2026

Copy link
Copy Markdown
Member Author

updated based on latest learnings and experiments from #726

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.

2 participants