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

Henrykie/helix swarm #306

Merged
merged 7 commits into from
Sep 30, 2024
Merged

Henrykie/helix swarm #306

merged 7 commits into from
Sep 30, 2024

Conversation

henrykie
Copy link
Contributor

@henrykie henrykie commented Sep 23, 2024

Issue number:
closes #41
closes #294

Summary

General improvements to the Perforce Helix Swarm module, and Perforce Helix Swarm example configurations.

Changes

Please provide a summary of what's being changed

= Replace Redis sidecar container with Elasticache.
= Adds SSO enable flag to Helix Swarm module.

  • Minor changes to formatting on HAS module.
  • Adds example configuration that provisions Helix Core, Helix Swarm, and Helix Authentication Service.

User experience

Please share what the user experience looks like before and after this change

  • Users should specify enable_sso to configure Swarm to use the SSO login page.
  • Redis is no longer configured as a sidecar in the Helix Swarm module. Instead, Helix Swarm now uses an Elasticache cluster it provisions itself. If you would like to use an external redis connection this can be passed through the existing_redis_connection variable.
  • Users can refer to the "complete" example under the Perforce module for a Helix Core, Helix Swarm, Helix Authentication Service configured deployment.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

  • I have performed a self-review of this change
  • Changes have been tested
  • Changes are documented
Is this a breaking change?

Yes. This does replace the existing Redis sidecar container in the Helix Swarm module with a dedicated Elasticache cluster.

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created might not be successful.

@henrykie henrykie requested a review from a team as a code owner September 23, 2024 02:19
@henrykie henrykie requested a review from jorisdon September 23, 2024 02:19
modules/perforce/examples/complete/dns.tf Dismissed Show dismissed Hide dismissed
modules/perforce/examples/complete/dns.tf Dismissed Show dismissed Hide dismissed
modules/perforce/examples/complete/dns.tf Dismissed Show dismissed Hide dismissed
modules/perforce/examples/complete/dns.tf Dismissed Show dismissed Hide dismissed
modules/perforce/examples/complete/vpc.tf Dismissed Show dismissed Hide dismissed
modules/perforce/examples/complete/vpc.tf Dismissed Show dismissed Hide dismissed
@henrykie henrykie added perforce terraform Pull requests that update Terraform code labels Sep 23, 2024
@henrykie henrykie force-pushed the henrykie/helix-swarm branch from db6c82a to 3529f3f Compare September 23, 2024 03:45
gabebatista
gabebatista previously approved these changes Sep 27, 2024
Copy link
Contributor

@gabebatista gabebatista left a comment

Choose a reason for hiding this comment

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

lgtm, made some minor comments on naming standard for fqdn prefix

modules/perforce/examples/complete/main.tf Outdated Show resolved Hide resolved
Copy link
Member

@kylesomers kylesomers left a comment

Choose a reason for hiding this comment

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

see inline comments. small fixes

docs/media/images/helix-swarm-architecture.jpg Outdated Show resolved Hide resolved
docs/media/images/helix-swarm-architecture.jpg Outdated Show resolved Hide resolved
@henrykie
Copy link
Contributor Author

@jorisdon @gabebatista @kylesomers I've made changes to the actual commit history on this branch to match Joris's git strategy as discussed. Individual commits can be reviewed as discrete pieces (swarm updates, core updates, etc...). This makes reviews easier. It also allows us to rebase the feature branch onto main and have each of these commits show up in changelog.

@henrykie henrykie force-pushed the henrykie/helix-swarm branch 3 times, most recently from f6425ef to 28710a7 Compare September 29, 2024 05:04
jorisdon
jorisdon previously approved these changes Sep 30, 2024
Copy link
Contributor

@jorisdon jorisdon left a comment

Choose a reason for hiding this comment

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

LGTM

docs/modules/perforce/examples/complete.md Outdated Show resolved Hide resolved
kylesomers
kylesomers previously approved these changes Sep 30, 2024
@henrykie henrykie dismissed stale reviews from kylesomers and jorisdon via 87e1578 September 30, 2024 23:12
@henrykie henrykie force-pushed the henrykie/helix-swarm branch from 28710a7 to 87e1578 Compare September 30, 2024 23:12
@henrykie henrykie removed the request for review from gabebatista September 30, 2024 23:16
@henrykie henrykie merged commit 6cc2dd8 into main Sep 30, 2024
7 checks passed
@henrykie henrykie deleted the henrykie/helix-swarm branch September 30, 2024 23:33
jcwolfaws pushed a commit to jcwolfaws/cloud-game-development-toolkit that referenced this pull request Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perforce terraform Pull requests that update Terraform code
Projects
None yet
4 participants