Skip to content

Do not override orchestratord version by default. #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

alex-hunt-materialize
Copy link
Contributor

Do not override orchestratord version by default.

The helm chart includes the orchestratord version, and people should probably just use the default in 99% of cases. We also don't want to have to keep updating these examples every time the version changes.

Copy link
Collaborator

@bobbyiliev bobbyiliev left a comment

Choose a reason for hiding this comment

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

Nice!

@bobbyiliev
Copy link
Collaborator

I had a tracking issue for this: #16 we could do the same in the downstream modules as well.

@alex-hunt-materialize
Copy link
Contributor Author

I had a tracking issue for this: #16 we could do the same in the downstream modules as well.

My certificate PRs do this for the downstream modules :)

@alex-hunt-materialize alex-hunt-materialize merged commit 7d3973a into main Mar 27, 2025
1 check passed
@alex-hunt-materialize alex-hunt-materialize deleted the default_to_not_overriding_orchestratord_version branch March 27, 2025 11:54
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