Moving the code for deploying configs to the agent-host-charm from the agent-charm means that we can update all the configs at once. This should be a lot faster and easier to manage. The charm needs a place to pull them from. Right now, we store them in git, so it makes sense to add a config option for the git repo and path for the part of that repo that contains the configs this agent host should look at. NOTE: this does NOT tie us to using git forever. If a better option emerges, then we could support that in addition to, or instead of this.
The configs are not static. Agents will be added, removed, and changed over time. There should be a juju action that allows us to trigger an update to the agent configs.
Resolved issues
CERTTF-377
Documentation
Updated README
Web service API changes
N/A
Tests
Updated unit and integration tests
NOTE: For the integration tests, I added some data to THIS branch, and used config settings we provide here to force it to get that test data from this branch. Eventually, when this lands, we'll want to update this to point to main instead, but that's not something we can change until this lands.
Description
Moving the code for deploying configs to the agent-host-charm from the agent-charm means that we can update all the configs at once. This should be a lot faster and easier to manage. The charm needs a place to pull them from. Right now, we store them in git, so it makes sense to add a config option for the git repo and path for the part of that repo that contains the configs this agent host should look at. NOTE: this does NOT tie us to using git forever. If a better option emerges, then we could support that in addition to, or instead of this.
The configs are not static. Agents will be added, removed, and changed over time. There should be a juju action that allows us to trigger an update to the agent configs.
Resolved issues
CERTTF-377
Documentation
Updated README
Web service API changes
N/A
Tests
Updated unit and integration tests
NOTE: For the integration tests, I added some data to THIS branch, and used config settings we provide here to force it to get that test data from this branch. Eventually, when this lands, we'll want to update this to point to main instead, but that's not something we can change until this lands.