- Adds groovy to the series in the metadata
- Classic charms: sync charm-helpers.
- Classic ceph based charms: also sync charms.ceph
- Reactive charms: trigger a rebuild
Change-Id: I52455cf6a97b72329b060da281b7e12ded9cc8fc
* remove resources from the smoke test bundle
* attach_saml_resources step in Zaza does it https://git.io/JfKTp
* use the same set of applications in the smoke bundle so that configure
steps and func tests pass.
Change-Id: Ic5c7bbb479197b7bc7161c2cd6090984901fa2b6
Closes-Bug: #1881267
This patch adds a focal-ussuri bundle to the tests for the charm.
It also cleans up the tests.yaml and stops it doing the same test twice
for gate.
Change-Id: I290c089c9a20a946ec8da240e9c83d16a2cbbb03
See "4.13.2. Service Provider Metadata" in mellon_user_guide.
Note: SOAP reversed: PAOS
Change-Id: If94f9d306cb73e716560d608851412395adfe88d
Closes-Bug: #1833134
Allow the usage of an IDP discovery service for multiple IDPs.
Make use of "MellonDiscoveryURL" option in "mod_auth_mellon"
Apache module.
Change-Id: I2eed6dc3c57a51ed12f8ca4b31b46a13bc8fa911
Signed-off-by: Yanos Angelopoulos <yanos@admin.grnet.gr>
This is a mechanically generated patch to ensure unit testing is in
place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note that python35-charm-jobs is retained since this charm is supported
on Xenial.
Change-Id: I10bcd0c4847e2f0828c8df6d23d148d2b55c74f7
Story: #2005924
Task: #34228
Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata. Dev release tests are enabled separately
because of chickens and eggs.
Change-Id: I589617c4afaf21521d2231f5c00ca50c7df7df3e
Do not rely on system installed Python packages but distribute the
direct charm dependencies as part of the charms wheelhouse.
As the span of distributions we need to support with reactive
charms widens we will run into compability problems with the
current model.
For further reference see juju/charm-helpers#341 and
juju-solutions/layer-basic#135
Change-Id: I11fb4020dc358c40bf9c1870e94186ba7e97c2db
get-sp-metadata action hardcodes the location of an sp metadata file
which is incorrect - it should use the application name to allow custom
application names and usage of multiple keystone-saml-mellon
applications (to have multiple IdPs).
In order to make unit testing easier the global variable for the sp
metadata file in actions.py is moved into a function so that it is
evaluated at the function call time, not module import time.
Change-Id: Ia73cd633f2948080e9a892869074ed2775ecc33c
Closes-Bug: #1833202
LP: #1334482 and LP: #1832605 summarize the issue.
Until the larger problem is fixed we can fix the immediate one by not
using Unicode quotes in metadata.yaml.
Change-Id: I21249679ac9aa107c0bede96a07e5d6e0b7218a8
Closes-Bug: #1832605
This testing setup gets us 3/4 of the way to a full functional test and
is a step toward a full solution.
The tests will validate Service Provider (SP) metadata and the redirect
relationship between horizon, keystone and the IDP. Samltest.id is used as
the IDP which is currently accessible through our firewalling.
What we are not yet doing is publishing the SP metadata in the IDP and doing
a full login on the IDP.
Merge Zaza change first:
https://github.com/openstack-charmers/zaza/pull/230
Aurelien Lourot
Alex Kavanagh
David Ames
Hervé Beraud
Dmitrii Shcherbakov
Zuul
Ryan Beisner
Claudio Pisa
Yanos Angelopoulos
Corey Bryant
Chris MacNaughton
Frode Nordahl
James Page
Ryan Beisner
Frode Nordahl
David Ames