Adds a workflow to create an AIO #1150
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is useful for debugging.
Remove file as I'm testing in the other one
markgoddard
reviewed
Jul 11, 2024
| @@ -1,328 +1,36 @@ | |||
| --- | |||
Contributor
Author
There was a problem hiding this comment.
Oh, it so I could test it before merging. I needed the action to already exist in https://github.com/stackhpc/stackhpc-kayobe-config/actions
to be able to trigger it before merging . The idea was to move to a new file once it worked. Not sure if there is an easier way?
Contributor
There was a problem hiding this comment.
perhaps add a workflow_dispatch trigger to the PR workflow?
Alex-Welsh
added
enhancement
Member
|
This looks handy, @jovial is there any chance of it being resurrected? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This creates an AIO with the usual workflow but doesn't delete it. The idea is you can login with a secondary key and debug why the failure is occurring. Just remember to manually delete the VM afterwards.