RING-43206 - Create and Remove offline installer workflows

[TrevorBenson]

• What's the goal of each workflow?

• create-offline-installer.yml

  1. Generate an SFX (Self Extracting-Archive) containing:
     • spark tool (python scripts to submit to the Spark/Hadoop cluster)
     • ansible playbooks for deployment
     • container images to push/load (spark master & worker, nginx, s3utils)
  2. Based on prerelease or GA tag the image w/ a version or "prerelease" for testing a new release prior to tagging.
  3. Upload the archive to the packages.scality.com/extras/ path for TS/Customer access.

• remove-offline-installer.yml

  1. Remove an SFX from the packages.scality.com server
     • handle retention so a limited set of prior versions are available.
     • reduce storage bloat

• When are those workflow triggered, consistently after each release? Sometimes?

• Currenlty they are triggered on manual workflow_dispatch.
• Deployment protection rules requiring approval to actually run the workflow are in place.

• Are you triggering multiple workflows when making a release?

• One workflow to start, two when we want to cleanup older versions.
• Once there are too many old versions available then the remove-offline-installer.yml would be run manually to target a specific version to remove.
  • Initially only 1 or 2 prior versions would be kept with the latest version.