The following PR adds a --variable flag for the draft update command, which makes it possible to run the command non-interactively.
This makes adding integration tests possible for the command, which this PR also adds.
Fixes # (issue)
Feature # (details)
Type of change
Please delete options that are not relevant.
[X] New feature (non-breaking change which adds functionality)
[X] This change requires a documentation update
How Has This Been Tested?
Integration tests have been added for the update command
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s).
Integration tests have been added for the draft update command for every existing integration scenario.
For linux helm and kustomize, the upgrade integration test was added to the existing integration test that is validated by confirming successful deployment to minikube.
For the the linux manifets deployment and all the windows deployments integration tests a new dependent job was added to run after the draft create integration test that re-uses artifacts and applies the draft update command yields files and executes without error.
Template contents verification for the update command isn't included at this time.
Checklist:
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
Description
The following PR adds a
--variable
flag for thedraft update
command, which makes it possible to run the command non-interactively. This makes adding integration tests possible for the command, which this PR also adds.Fixes # (issue) Feature # (details)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Integration tests have been added for the
update command
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s).
Integration tests have been added for the
draft update
command for every existing integration scenario. For linux helm and kustomize, the upgrade integration test was added to the existing integration test that is validated by confirming successful deployment to minikube. For the the linux manifets deployment and all the windows deployments integration tests a new dependent job was added to run after thedraft create
integration test that re-uses artifacts and applies thedraft update
command yields files and executes without error. Template contents verification for the update command isn't included at this time.Checklist: