Add initial support for Packer in Orka #3872
Merged
Conversation
This file contains 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
12 tasks
UlisesGascon
force-pushed
the
feat/orka-packer
branch
from
7b5e630
to
320a296
Compare
mhdawson
approved these changes
Aug 27, 2024
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.
Main Changes
The main goal is to add support for Packer in Orka and validate the templates in future PRs.
Details
.envfiles inorka/folder and subfoldersScreenshots
The template is working good enough for what is expected in this PR (communication, creation and CI validation)
Context
This PR is part of the Orka plan described in #3686 (comment)
Notes
The CI passed including the new pipeline execution details
The CI won't handle the image publication, just the validation when we do changes in the templates. All the deployment will remain manually done by the infra admins (as usual).