Merge ~mthaddon/charm-k8s-gunicorn/+git/charm-k8s-gunicorn:pebble into charm-k8s-gunicorn:master
Status: | Work in progress |
---|---|
Proposed branch: | ~mthaddon/charm-k8s-gunicorn/+git/charm-k8s-gunicorn:pebble |
Merge into: | charm-k8s-gunicorn:master |
Diff against target: |
577 lines (+329/-89) (has conflicts) 6 files modified
lib/charms/nginx_ingress_integrator/v0/ingress.py (+174/-0) metadata.yaml (+15/-0) requirements.txt (+1/-1) src/charm.py (+136/-66) tests/unit/scenario.py (+3/-0) tests/unit/test_charm.py (+0/-22) Conflict in metadata.yaml Conflict in src/charm.py Conflict in tests/unit/scenario.py |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
gunicorn-charmers | Pending | ||
Review via email: mp+399520@code.launchpad.net |
Commit message
Test of pebble version of the charm
Description of the change
Test of pebble version of the charm.
$ git clone -b 2.9 https:/
$ cd juju
$ make install
$ make microk8s-
$ export PATH="/
$ juju bootstrap microk8s
$ juju add-model gunicorn
$ juju deploy ./gunicorn.charm --resource gunicorn-
Once deployed, check juju status for the IP address and then visit that in a browser. You should see something like:
------------------
One of the nice things about the new operator framework is how easy it is to get started.
KUBERNETES_
KUBERNETES_
GUNICORN_PORT: tcp://10.
HOSTNAME: gunicorn-0
JUJU_CONTAINER_
MODELOPERATOR_
GUNICORN_
PEBBLE_SOCKET: /charm/
PWD: /srv/gunicorn
HOME: /root
KUBERNETES_
GUNICORN_
MODELOPERATOR_
GUNICORN_
GUNICORN_
GUNICORN_
APP_WSGI: app:app
APP_NAME: my-awesome-app
SHLVL: 0
MODELOPERATOR_
KUBERNETES_
KUBERNETES_
MODELOPERATOR_
GUNICORN_
MODELOPERATOR_PORT: tcp://10.
KUBERNETES_
KUBERNETES_PORT: tcp://10.
KUBERNETES_
PATH: /usr/local/
GUNICORN_
MODELOPERATOR_
DEBIAN_FRONTEND: noninteractive
MODELOPERATOR_
LC_CTYPE: C.UTF-8
SERVER_SOFTWARE: gunicorn/20.0.4
------------------
To test juju config updates, create a yaml file with the following sample contents:
FOOD: burgers
DRINK: ale
Then run `juju config gunicorn environment=
This charm handles an upgrade-charm hook (assuming it's not failing due to config issues as above.
Next steps:
- Handle relations.
- Update unit tests.
- Document missing functionality versus the current implementation.