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

Update the AMI update workflow #77

Merged
merged 9 commits into from
Aug 29, 2023
Merged

Conversation

mavimo
Copy link
Contributor

@mavimo mavimo commented Aug 28, 2023

No description provided.

Running `updatecli` as a matrix is preferred because it simplifies the management of
needing to update several families of OS types in a common, but separate manner.
Unfortunately there appears to be an odd behavior with parallel executions of the
updatecli tool that results in each parallel run of the matrix using the same git branch
name, which results in a combination of either experienceing git fast-forward errors, or
more than one OS family's worth of updates on the same PR. This change restricts the matrix
to only being able to run serially until a more optimal solution can be found.
Due to `updatecli` creating a hash of the config files before the templates
are rendered, all runs of `updatecli` triggered by GitHub were using the
same branch name, which was causing collisions. this change modifies
the workflow to use `envsubst` to template out the new config files
before handing them to `updatecli` so that the generated hashes, and
therefore branch names, are different so that we get unique PRs per
OS and driver type
* the value for OWNER_ID was being converted to exponential values
  by the go templating engine and needed to be quoted so that they
  were evaluated as strings
* fix the `if "a" == "b"` logic in favor of the correct `if eq "a" "b"`
  logic
@aroberts87 aroberts87 enabled auto-merge (squash) August 29, 2023 12:59
@aroberts87 aroberts87 merged commit 1a9bcdf into main Aug 29, 2023
@aroberts87 aroberts87 deleted the feat/adjust-updatecli-workflow branch August 29, 2023 15:52
@mavimo mavimo added this to the 0.1.0 milestone Oct 23, 2023
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

Successfully merging this pull request may close these issues.

2 participants