You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a breaking change for existing users?
Dont think so.
If modification is in Ansible scripts only, this should not cause destruction of EC2 infrastructure. Clients are directed to use an external database to protect their data anyways. We should confirm though.
Can extra Ansible steps be removed in favour of installing packages directly via yum?
This would be preferable but we need to see how the installation part meshes with later Ansible-specific modules like community.docker.docker_compose_v2
Given my recent efforts to get this running on localstack to speed up testing, I think this is definitely worth doing for a bunch of reasons, but I'm looking for sober second opinions (please).
The official Seqera installation documentation has been updated to use
docker compose
overdocker-compose
.The installer uses the old
docker-compose
solution (requiring the download of a separatedocker-compose
package).We should modify the project to align with the official docs.
Benefits:
01_load_sytem_packages
)Considerations:
Is this a breaking change for existing users?
Dont think so.
If modification is in Ansible scripts only, this should not cause destruction of EC2 infrastructure. Clients are directed to use an external database to protect their data anyways. We should confirm though.
Can extra Ansible steps be removed in favour of installing packages directly via
yum
?This would be preferable but we need to see how the installation part meshes with later Ansible-specific modules like
community.docker.docker_compose_v2
Alignment with testing implementation?
How will this impact pre-release testing is TBD.
The text was updated successfully, but these errors were encountered: