This commit adds support for Designate zones. This can be used to
provide the user a drop down list of zones they can choose from when
launching apps.
This should be coupled with a commit to murano to add a new
io.murano.resources.RecordSet resource type, so that new a new DNS
record can be added for new apps.
Change-Id: I71deb3e264b2777ec4126d8e46c3ac45b9fc42c6
The patch 7f29364734 removes the lower-constraints job from
the gate but related file like lower-constarints.txt are not
removed. This patch removes the lower-constraints.txt file and
its reference from tox.ini.
Also TC passed a resolution about dropping the lower-constraints.txt
file and its testing. We will keep lower bounds in the requirements.txt
file but with a note that these are not tested lower bounds and we
try our best to keep them updated. For more info please refer [1], [2].
[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal
Change-Id: Ica7454c88d17874ed29c5d29d399ba5684f7f9d1
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: I5ad2c7a44dee2e19ab2576f206c69d94126a22b1
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Co-Authored-By: zhurong <aaronzhu1121@gmail.com>
This repo does not support Python 2 anymore, so we don't need
six for compatibility between Python2 and 3, convert six usage to Python
3 code.
Change-Id: Ibc743a552a43147153dd0ca3a46ab8d977c7ca0d
Django 1.11 ends its extended support in April 2020 (which is before
Ussuri release), so horizon drops Django 1.11 support in Ussuri.
tox envs for non-primary Django versions are no longer needed in tox.ini
as testing environments for non-primary Django versions are setup in
the zuul jobs now.
horizon>=17.1.0 is required to use Django 2.2. requirements.txt and
lower-constraints.txt are updated accordingly. for more info. please
refer [1].
Depends-On: https://review.opendev.org/#/c/700733/
[1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin
Change-Id: I59e016fd771282798bd095c562e2fa11a8e4ea43
We have switched the babel extractor for Django from django-babel
to enmerkar recently. murano-dashboard requirements.txt needs to
sync the change. enmerkar, a successor of django-babel will be
installed via horizon, so we don't need to have it in requirements.txt
explicitly.
lower-constrants.txt is updated to use enmerkar accordingly.
Change-Id: Iab0a50a6f6546d3d67d0e9b00f9bbd04ee2f6c7c
django-floppyforms is not very well supported anymore
and was dropped from Ubuntu in Xenial.
Closes-bug: #1805193
Change-Id: I46bf2d43794a67a4dc080afa9f1740a582cb7631
In Stein development version of horizon, APITestCase and APIMockTestCase
are identical, and APIMockTestCase will be dropped in future.
murano-dashboard is the only consumer of APIMockTestCase now.
This commit clean up the usage of APIMockTestCase.
horizon stein depends on osprofiler>=2.3.0, so lower-constraints.txt
file is updated accordingly.
Change-Id: I36cb8ade8ec80cd313dc9be9e1f1a67daeb60c87
As of horizon 14.0.0.0b2 or later the use_mox directive is unecessary
so we can remove it.
Additionally:
* Drop mox3 from test-requirements.txt
* raise lower bound for Horizon (due to mox3 removal)
Change-Id: Ibcdd5fcda789a4038a538b19d09bc87cdc6fe7f3
Signed-off-by: Chuck Short <chucks@redhat.com>
Previously install_command specifies upper-constraints
so lower-constraints actually did not work.
upper-constraints must be specified via 'deps' instead of 'install_command'.
The fix reveals that django-formtools 1.0 is not compatible with
Django 1.11 or later. django-formtools 2.0 seems the minimum requirement.
Castellan 0.16.0 is not compatible with murano-dashboard because there is
barbican_endpoint_type. The minimum required version is 0.18.0.
This commit also drops Django dependency in requirements.txt.
After commit 7e91070789187d9e6b5ac2b57ca755504e058e32 in
openstack/requirements repo, all project requirements.txt must
have lower bounds and Django entry hits this.
Horizon declares django dependencies, so there is no need to
declare django dependencies in murano-dashboard explicitly.
Change-Id: I3048ca5570523494f5a58a15449902f8cb3eb3a4
Replace django.core.urlresolves with django.urls
(In Django 2.0) The django.core.urlresolvers module is removed
in favor of its new location, django.urls.
It was deprecated in Django 1.10:
https://docs.djangoproject.com/en/2.0/releases/1.10/#id3
Add py35dj20 job to test Django 2.0 integration.
And update the lower-constraints.
Co-Authored-By: Akihiro Motoki <amotoki@gmail.com>
Co-Authored-By: Ellen Batbouta <ellen.batbouta@oracle.com>
Change-Id: I3456162c934eb48ccf180d80b5cf7ff5614221c0
Adds a new yaql function 'encryptData' which encrypts values passed from
MuranoPL UI definitions.
Requires a valid secret storage backend (e.g. Barbican) to be configured
via Castellan in _50_murano.py
Murano will still work fine without this config but the encrypt/decrypt
functions will be unavailable.
Implements blueprint: allow-encrypting-of-muranopl-properties
Depends-On: I09416b6d35ed2dafa823eca98262a4e23081e6eb
Change-Id: Ida94093425a113b67baa05a194525e3cf4e16f79
Fetch local timezone from session variable 'django_timezone'. This
setting can be either set in Horizon manually or it defaults to the
value of setting TIME_ZONE (with 'UTC' value as a default).
Change-Id: I6c0bbf7b0e0763bd238ab9fa9c4c75e3fdf02fbd
Tri-state checkbox is the kind of checkbox which has three states
instead of two, as the regular checkbox has.
Third state is "indeterminate", which means, that the element is in
undefined state. Common example of such situation is some parent
element, which has some of child elements selected and some not - and
so it means that parent element is not selected nor unselect - which
in terminology of this changeset called "indeterminate" state.
Partially implements bp assign-category-button
Depends-On: Ie65a77eab29aa191420fbd630b1d242b59c9ff9f
Change-Id: I98116fce362af5eb4c64941f4c442dd81120e762