Stabilization of Verisioning and Predictable Defaults

[galenatjpl]

• Create "24.4-stable" versions of the marketplace items in marketplace_config.yaml

ManagementConsole:
sha: 
release: <STABLE_24.4_RELEASED_VERSION_OF_MC>

MarketplaceItems:
  - name: unity-cs-monitoring-lambda
    version: 24.4-stable
  - name: unity-apigateway
    version: 24.4-stable
  - name: unity-proxy
    version: 24.4-stable
  - name: unity-ui
    version: 24.4-stable

• Add new flag to run.sh, where you can specify the config YAML file to use. DOES THIS ALREADY EXIST AS --config-file ?

• Create "latest" versions for each marketplace folder/item

• Add a --latest flag. This would be a flag used primarily by U-CS developers that would indicate that each value in the config file should be set to latest.

• Add individual override version flags like unity-apigateway-version, unity-proxy-version, etc..

• Dynamically construct marketplace_config_working.yaml, which would apply any override version flag values, or simply copy the base config to marketplace_config_working.yaml. This marketplace_config_working.yaml file would be the one ALWAYS used by the run.sh/deploy.sh scripts.

• Modify marketplace_config.yaml to have all entries reference the "24.4-stable" MP items, which will be the default used, if no "config-file" flag is specified.

• Modify structure of yaml to include a MC commit or release:

ManagementConsole:
sha: <COMMIT_SHA>
release: <RELEASE_VERSION>

MarketplaceItems:

name: unity-cs-monitoring-lambda
version: 0.1
name: unity-apigateway
version: 0.4
name: unity-proxy
version: 0.14
name: unity-ui
version: 0.8.0

• if sha exists, then it takes precedent over release. release is the existing mechanism that uses MCVersion variable in the cloudformation template.
• Modify run.sh to pass new sha value
• Modify deploy.sh to accept sha value
• Modify deploy.sh to pass sha to cloudformation alongside the existing MCVersion argument
• Modify cloudformation template to have shell logic that uses sha OR release conditionally, and does a git pull / git checkout appropriately, and run Go code that builds a release locally.

NOTE: the code changes may have to be done in the monorepo. Please confirm with @jimmie