[wip] facade charm #152
[wip] facade charm #152
Conversation
|
|
it's somewhat similar to https://github.com/canonical/any-charm but less focused on programming the charm itself and more focus on the interfaces |
| @@ -0,0 +1,239 @@ | |||
| interfaces: | |||
There was a problem hiding this comment.
We should probably add a comment to mention that this file is automatically generated and should not be modified.
| @@ -0,0 +1,15 @@ | |||
| # Copyright 2024 pietro | |||
There was a problem hiding this comment.
| # Copyright 2024 pietro | |
| # Copyright 2024 Canonical Ltd. |
Co-authored-by: Guillaume Belanger <[email protected]>
| resp = requests.get("https://charmhub.io/packages.json") | ||
| return resp.json()['packages'] |
There was a problem hiding this comment.
Consider adding resp.raise_for_status();
or possibly configuring the client to automatically raise for bab status values.
There was a problem hiding this comment.
OT: this gives me exactly 360 charms packages.
I wonder if that's all there is, or is it some kind of server limit?
|
|
||
|
|
||
| async def get_all_integrations(charms_pkg_info): | ||
| async with aiohttp.ClientSession() as session: |
There was a problem hiding this comment.
| async with aiohttp.ClientSession() as session: | |
| async with aiohttp.ClientSession(raise_for_status=True) as session: |
I would also include a base URL, it's pretty handy.
This PR adds a
facadecharm to this repository.The facade charm is a 'universal prorgrammable relation interface mocking charm'.
Charmcraft.yaml is dynamically generated, and to help people remember that they should regenerate it on each use, it's generated by
tox -e packand deleted afterwards.The idea is:
Purpose:
See it in action:
https://github.com/canonical/tempo-k8s-operator/pull/127/files#diff-0b4ff0c5a367926f20bde3d63ac17e8a1b14a6459e6a05e2ec6a0e2c654c1e3c