-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Support legacy 'import' directive and use 'imports' for future (#…
…543) * feat: Support legacy 'import' directive and use 'imports' for future This changes the behavior of the 'import' target to behave as it did before the breaking change that moved imports into /stacker/imports/ So now, if the stacker file uses 'import', then imports will be placed in /stacker. If the stacker file uses 'imports' (plural) then they will be placed in /stacker/imports. What we actually get in both cases is a consistent set of binds being done into a different "base". Either /.stacker (legacy) or /stacker (new). stacker -> <base>/bin/stacker imports -> <base>/imports runscript -> <base>/imports/.stacker-run.sh artifacts -> <base>/artifacts In the legacy case, the imports are also bind-mounted into /stacker Signed-off-by: Scott Moser <[email protected]> * test: replace import with imports, add one explicit legacy import test This just changes all the existing tests to test 'imports' rather than 'import'. Then it adds one test for 'import' explicitly and within the same stacker file. Test test/cache.bats test "can read previous version's cache" is skipped as the old version can't build a stacker file in the test because it uses 'imports'. Signed-off-by: Scott Moser <[email protected]> --------- Signed-off-by: Scott Moser <[email protected]>
- Loading branch information
Showing
28 changed files
with
244 additions
and
150 deletions.
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.