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

[ Maintenance ] Update solution to support SP Enterprise v24.3 #186

Open
2 of 12 tasks
gwright99 opened this issue Feb 27, 2025 · 1 comment
Open
2 of 12 tasks

[ Maintenance ] Update solution to support SP Enterprise v24.3 #186

gwright99 opened this issue Feb 27, 2025 · 1 comment
Assignees

Comments

@gwright99
Copy link
Collaborator

gwright99 commented Feb 27, 2025

Update as per:

Note

I initially tried to create these tasks as github sub-issues, but the mechanism didn't work as I expected it to. #187, #188 , #189 , and #190 have all been closed and their tasks ported here for simplicity of management.

Tasks

  • Update `templates/TEMPLATE_terraform.tfvars':
    • Update data_studio_container_version = 0.7.8.
  • Assess Security Contexts and whether changes required to docker-compose file:
    • connect proxy
    • connect server
  • Implement pre-deployment checks:
    • Ensure v0.7.8 is not run with a version of SP Enterprise < v24.2.x .
    • Ensure data_studio_container_version is populated with a viable version (e.g. 0.7.0, 0.7.1, 0.7.2, and 0.7.8 -- confirm exact list with DS team)
  • Seqera-managed Studios containers:
    • Confirm with Product if any more managed container entries need to be added.
    • Update configuration structure (if necessary).
  • Change CONNECT_SERVER_LOG_LEVEL to CONNECT_LOG_LEVEL
@gwright99 gwright99 self-assigned this Feb 27, 2025
@gwright99
Copy link
Collaborator Author

gwright99 commented Feb 27, 2025

Implementation Decisions

  1. Stick with data_studio nomeclature.

    The official product has been renamed to Studios (no longer Data Studios). Given that the solution already has long-established divergences (e.g. tower instead of seqera_platform), and that modifying terraform.tfvars keys will require additional manual intervention by implementers, I'm sticking with the pre-existing data_studio nomenclature (sorry Product).

    This can be aligned in a Version 2.0.

This was linked to pull requests Feb 27, 2025
This was unlinked from pull requests Feb 27, 2025
@gwright99 gwright99 linked a pull request Feb 27, 2025 that will close this issue
@gwright99 gwright99 mentioned this issue Feb 27, 2025
2 tasks
@gwright99 gwright99 marked this as a duplicate of #188 Feb 27, 2025
@gwright99 gwright99 marked this as a duplicate of #189 Feb 27, 2025
@gwright99 gwright99 marked this as a duplicate of #190 Feb 27, 2025
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

No branches or pull requests

1 participant