Skip to content
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

DM-48364: mobu - update docs #4054

Merged
merged 1 commit into from
Jan 9, 2025
Merged

Conversation

fajpunk
Copy link
Member

@fajpunk fajpunk commented Jan 8, 2025

No description provided.

@fajpunk fajpunk requested review from rra and jonathansick January 8, 2025 21:26
@fajpunk fajpunk force-pushed the tickets/DM-44145/mobu-docs-update branch from 9dea6ea to d92bb91 Compare January 8, 2025 21:30
Copy link
Member

@rra rra left a comment

Choose a reason for hiding this comment

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

I think we talked about this, but I don't remember the result: I think we decided that we were going to inject this value via Argo CD based on the environment configuration so that, eventually, no one needs to set this manually, right?

applications/mobu/tests/github_ci_app_enabled_test.yaml Outdated Show resolved Hide resolved
applications/mobu/values.yaml Outdated Show resolved Hide resolved
@fajpunk fajpunk force-pushed the tickets/DM-44145/mobu-docs-update branch from dd05f8e to ad879e6 Compare January 8, 2025 21:45
@fajpunk
Copy link
Member Author

fajpunk commented Jan 8, 2025

I think we talked about this, but I don't remember the result: I think we decided that we were going to inject this value via Argo CD based on the environment configuration so that, eventually, no one needs to set this manually, right?

Yep, ideally no one has to set this manually, but I didn't think we decided exactly how we were going to do it. Is it possible to do it from the ArgoCD environment now? Other than doing something like parsing the environments/ values yaml files somehow?

Copy link
Member

@jonathansick jonathansick left a comment

Choose a reason for hiding this comment

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

It's besides this review but I noticed that Mobu has two GitHub Apps now. Did you consider having one app and putting either a configuration file in the target repos or configuration in Phalanx saying what operations are enabled on that repo?

applications/mobu/values.yaml Outdated Show resolved Hide resolved
applications/mobu/values.yaml Outdated Show resolved Hide resolved
applications/mobu/values.yaml Outdated Show resolved Hide resolved
@fajpunk fajpunk force-pushed the tickets/DM-44145/mobu-docs-update branch 2 times, most recently from 5d98c5a to ebe07c8 Compare January 9, 2025 17:26
review feedback

Change raw URLs to markdown links

here -> the Mobu documentation
@fajpunk fajpunk force-pushed the tickets/DM-44145/mobu-docs-update branch from ebe07c8 to 47ad162 Compare January 9, 2025 17:26
@fajpunk fajpunk enabled auto-merge January 9, 2025 17:26
@fajpunk fajpunk added this pull request to the merge queue Jan 9, 2025
Merged via the queue into main with commit bd63077 Jan 9, 2025
7 checks passed
@fajpunk fajpunk deleted the tickets/DM-44145/mobu-docs-update branch January 9, 2025 17:40
@fajpunk
Copy link
Member Author

fajpunk commented Jan 9, 2025

Did you consider having one app and putting either a configuration file in the target repos or configuration in Phalanx saying what operations are enabled on that repo?

A few reasons, not all of them particularly convincing :)

  • We never want the CI functionality enabled in production environments. This could be configured in Phalanx though.
  • Different repos may want to do their CI in different environments.
    • The CI environments could be configured in an in-repo config file, but then Mobu would have to clone the repo and check the config file for every check_run and check_suite event. That would probably be fine
    • The repos that an env handles CI for could be configured in Phalanx. This could be a slight pain for new repos, but maybe is more in the spirit of using Phalanx as the source of truth for platform configuration.

@frossie
Copy link
Member

frossie commented Jan 9, 2025

I think we talked about this, but I don't remember the result: I think we decided that we were going to inject this value via Argo CD based on the environment configuration so that, eventually, no one needs to set this manually, right?

I think this is a placeholder pending service discovery?

@fajpunk
Copy link
Member Author

fajpunk commented Jan 9, 2025

I think we talked about this, but I don't remember the result: I think we decided that we were going to inject this value via Argo CD based on the environment configuration so that, eventually, no one needs to set this manually, right?

I think this is a placeholder pending service discovery?

Yep, and the Argo CD injection was done in this PR.

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.

4 participants