Write an integration test for GH: #780
Bug #1922801 reported by
Dan Watkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Wishlist
|
Thomas Stringer |
Bug Description
The code in https:/
To post a comment you must log in.
In #780, I mentioned some framework changes would be required. Specifically, I think we want to introduce a new mark[0] which allows us to configure the SSH keys that will be passed to the instance under test. An example of the introduction of a new mark is [1]: you can see that it uses `getter` to fetch the "lxd_config_dict" mark and then, with a cloud-specific guard, sets it in `launch_kwargs` (which is then passed to pycloudlib, our cloud library).
This would be similar, but would set `vm_params` in `launch_kwargs`: the provided `vm_params` is merged over the default config in [2] (so, yes, you're going to pass in a very deeply-nested dict): we can use that to pass in our non-standard key material. An important assumption by me here is that putting the non-standard key material here means that it will be presented to instances in a way that triggers this bug: please do confirm that!
I'm finishing my day here, please do ask follow-up questions: here or, as always, in #cloud-init!
[0] https:/ /docs.pytest. org/en/ stable/ example/ markers. html#mark- examples /github. com/canonical/ cloud-init/ commit/ 05216aa37e1fad3 2433dbea102dc3c eae7d8565d# diff-fa8021f770 4bd878dc75be40d 940098cdc526576 07b02fe6bf3acac 60ff10694 /github. com/canonical/ pycloudlib/ blob/main/ pycloudlib/ azure/cloud. py#L337- L345
[1] https:/
[2] https:/