MAAS

~troyanov/maas:proxy-headers

  1. Git
  2. lp:~troyanov/maas
  3. proxy-headers
Last commit made on 2023-03-14
Get this branch:
git clone -b proxy-headers https://git.launchpad.net/~troyanov/maas
Only Anton Troyanov can upload to this branch. If you are Anton Troyanov please log in for upload directions.

Branch merges

Branch information

Name:
proxy-headers
Repository:
lp:~troyanov/maas

Recent commits

8621fd0... by Anton Troyanov

fix(region): use $http_host to read Host header

$http_name
arbitrary request header field;

the last part of a variable name is the field name converted to lower case
with dashes replaced by underscores

f08e136... by Anton Troyanov

fix: set explicit testtools version

testtools 2.6.0 has a breaking change [1] that leads to an error:

    AttributeError: module 'email' has no attribute 'message'

[1]: https://github.com/testing-cabal/testtools/commit/b4bcd3c3d1964352d5f51def08629114057541a8

f2494d1... by Bill Wear

Update maas-offline-docs to 9c04e08f
[maas-documentation-25.html] fix duplicate url

ee94026... by Bill Wear

Update maas-offline-docs to 45e64ce5
Updated maas-documentation-25.md to current discourse version

020da05... by Bill Wear

Update maas-offline-docs to 0c4224ad
[maas-documentation-25.html] link in "how to operate maas" landing page

3e5e2f5... by Bill Wear

Update maas-offline-docs to 40523f25
Updated maas-documentation-25.md to current discourse version

f095359... by Bill Wear

Update maas-offline-docs to 39c5d696
[what-is-new-with-maas.html] fixes suggested by user

7ddfed4... by Peter Makowski <email address hidden>

Update maas-ui to 5eb2a4de9
refactor: replace Object entries method lookup (#4812)

3a34aef... by Bill Wear

Update maas-offline-docs to 371be1a3
Updated what-is-new-with-maas-5292.md to current discourse version

42cdcb5... by Björn Tillenius

Bug #2003310: Refresh scripts are not re-run if they pass, but fail to report the results to the region

While refreshing the hardware information for controllers,
the scripts might all pass, but when reporting the results
back to the metadata server, something went wrong.

The exception was swallowed and ignored, though, so the
networking service didn't noticed it and assumed that
all scripts had passed.

This changes things so that the signal exception is caught
in the networking service itself, so it's aware that something
went wrong.