-
Notifications
You must be signed in to change notification settings - Fork 102
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #949 from cderici/deploy-from-repository-new-endpoint
#949 #### Description This allows pylibjuju to use the new `DeployFromRepository` endpoint, introduced in the `Application` facade `v19`. `PendingUploadResources` will be handled in a separate PR. This also fixes what juju/juju@22e3fc0#diff-cd1b6b10813a1b0ebe7fe9a04f11c401dfeec0574ffb00058bfec98b6bb1d255 seems to be breaking by returning a non-empty error list `(Pdb) self.plan.errors ['', '', '', '', '', '', '', '', '']` from `GetChangesMapArgs`. #### QA Steps There's two parts for QAing this. Making sure deploy still works for everything `< 3.3`. CI tests will cover most of that part of the QA, as we use deploy in almost every single integration test, and it's being tested against `latest/stable` (which as of today is `3.1.5`). So it is advisable to do the manual QA (see below) against juju `3.2`, just to be sure. Second part is obviously making sure that the deploy works for `3.3` with the new endpoint. To do that, I simply ```sh $ juju version 3.3-beta2-ubuntu-amd64 $ juju bootstrap localhost lxd33 && juju add-model test ``` Then just manually deployed the `ubuntu` charm using repl. ```python python -m asyncio asyncio REPL 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] on linux Use "await" directly instead of "asyncio.run()". Type "help", "copyright", "credits" or "license" for more information. >>> import asyncio >>> from juju import model;m=model.Model();await m.connect();await m.deploy('ubuntu') <Application entity_id="ubuntu"> >>> exiting asyncio REPL... ``` All CI tests need to pass. #### Notes & Discussion JUJU-3637
- Loading branch information
Showing
15 changed files
with
55,573 additions
and
86 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
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
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
Large diffs are not rendered by default.
Oops, something went wrong.
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.