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

Enable 3 node deployment #249

Merged
merged 4 commits into from
Sep 30, 2024
Merged

Enable 3 node deployment #249

merged 4 commits into from
Sep 30, 2024

Conversation

Jorres
Copy link
Contributor

@Jorres Jorres commented Sep 26, 2024

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Other information

Migrating from 8-node YDB cluster with block-4-2 erasure to 3-node YDB cluster with mirror-3-dc erasure allowed us to run tests on top of Github runners, eliminating the need to supply secrets and a huge chunk of workflow YAML code.

Todo @Jorres: after this merges, remove unnecessary secrets from this repo

@Jorres Jorres force-pushed the enable-3-node-deployment branch from b1885ed to b211a27 Compare September 27, 2024 13:34
@Jorres Jorres force-pushed the enable-3-node-deployment branch from b211a27 to c1f9b14 Compare September 27, 2024 13:34
@Jorres
Copy link
Contributor Author

Jorres commented Sep 30, 2024

Cancelled tests are okay! The ones triggered by 'pull request' are the same as the one triggered by 'pull_request_target'. After this merges, the 'pull_request_target' will no longer exist and only one set of jobs, without check-pr, will run in the repository.

For the proof that an outside person can not run the workflow without approval, see this closed PR, which I opened from another account, not belonging to YDB Platform: #250

@Jorres Jorres merged commit a6b1501 into master Sep 30, 2024
4 of 6 checks passed
@Jorres Jorres deleted the enable-3-node-deployment branch September 30, 2024 11:44
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