Add auto-layer-releases flow to deploy flow

[hmstepanek]

Overview

Move auto-layer-releases flow from lambda to GHA.

[github-actions]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ YAML	prettier	1	0	0	0.43s
❌ YAML	v8r	1		1	1.72s
✅ YAML	yamllint	1		0	0.27s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.36%. Comparing base (25e1f1e) to head (da7cac0).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1274      +/-   ##
==========================================
- Coverage   79.55%   79.36%   -0.19%     
==========================================
  Files         201      201              
  Lines       22173    22173              
  Branches     3519     3519              
==========================================
- Hits        17639    17597      -42     
- Misses       3379     3431      +52     
+ Partials     1155     1145      -10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[TimPansino]

Suggested change

	#!/bin/bash
	#!/usr/bin/env python3

[TimPansino]

Why don't you make those a constant, so we don't have to set those as env vars? Presumably each repo will have a separate copy of this script.

[hmstepanek]

Well...I was still thinking of making it shared at this point (even though I realize I haven't done that in this PR). I guess TBD on that.

[TimPansino]

This originally had logic to have release names and release tags as different strings. For Python the only difference was capitalization, but for Node and .NET it was Node -> nodejs, and .NET -> dotnet.

Why not make constants for TAG_SUFFIX="python" and RUNTIME_NAME="Python". Then maybe use bool constants to toggle on/off the lambda and initcontainer releases?

[hmstepanek]

oooh you're totally right! I was trying to simplify those out but they were used for the release name-I'll put those back I guess. Instead of a boolean I was thinking each team could just set the value of those and that way the work flow could be shared across all teams-I need to look into that more though to see if we can do that.

[TimPansino]

As a general thought, is there a reason not to convert this to bash scripting and use the gh CLI? Seems like it would be easier for other teams to manage, and we could then just add the code directly into the release flow as a step.

[hmstepanek]

As a general thought, is there a reason not to convert this to bash scripting and use the gh CLI? Seems like it would be easier for other teams to manage, and we could then just add the code directly into the release flow as a step.

I was actually thinking about this after I pushed this up as a Python script. Since we seem to both have had that thought, I'll just go ahead and do that. I agree-it would be easier to maintain that way for each team in the long run.