summaryrefslogtreecommitdiff
path: root/setup.cfg
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Moves supported python runtimes from version 3.8 to 3.10"HEAD4.2.0masterGhanshyam2023-05-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 67a3d3b0db462949ebcc07f9b7c45559a29fde1f. Keeping Python 3.10 in setup.cfg classifier and zuul.yaml changes. Reason for revert: Needed-By: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175 TC has been discussing about re-adding the python 3.8 testing in current master 2023.2 release testing. - https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#l-191 - https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.html While governance changes are under review, TC agreed to add py3.8 testing so that we do not see more project/lib dropping python 3.8 and make them uninstalable on python 3.8 - https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-02-18.00.log.html#l-17 - https://review.opendev.org/c/openstack/governance/+/882165 Also adding py3.8 testing back in job https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175 Change-Id: I50a55442701be16bae3b7ae2035743b9f174dcfd
* Moves supported python runtimes from version 3.8 to 3.10Hervé Beraud2023-04-101-2/+2
| | | | | | | | Within 2023.2 python version 3.9 and 3.10 are the supported python runtimes [1]. [1] https://review.opendev.org/c/openstack/governance/+/872232 Change-Id: I82682282703def588ce95b9b0067651ccf5ce924
* Drop python3.6/3.7 support in testing runtimeHervé Beraud2022-05-051-3/+1
| | | | | | | | | | In Zed cycle testing runtime, we are targetting to drop the python 3.6/3.7 support, project started adding python 3.8 as minimum, example nova: - https://github.com/openstack/nova/blob/56b5aed08c6a3ed81b78dc216f0165ebfe3c3350/setup.cfg#L13 Change-Id: Icd143d8880666c1282e1e7821c108ab3e4de7813
* Update python testing classifierdengzhaosen2021-12-211-0/+1
| | | | | | | | | | | | | | Yoga testing runtime[1] has been updated to add py39 testing as voting. Unit tests update are handled by the job template change in openstack-zuul-job - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286 this commit updates the classifier in setup.cfg file. [1] https://governance.openstack.org/tc/reference/runtimes/yoga.html Change-Id: I977e8e5d1a4e4b4aeebf484cfb2fca28dec7b724
* setup.cfg: Replace dashes with underscoresyangyawei2021-05-141-4/+4
| | | | | | | | | | | | | | | | Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I58b9521882d81ab508bb7ce28308d88771daf1fe
* Add oslopolicy-convert-json-to-yaml toolGhanshyam Mann2020-08-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add ``oslopolicy-convert-json-to-yaml`` tool which can be used to convert the json formatted policy file to yaml format. It takes json formatted policy file as input and convert it to a yaml formatted policy file similar to 'oslopolicy-sample-generator' tool except keeping the overridden rule as uncommented. This tool does the following: * Comment out any rules that match the default from policy-in-code. * Keep rules uncommented if rule is overridden. * Does not auto add the deprecated rules in the file unless it not already present in the file. * Keep any extra rules or already exist deprecated rules uncommented but at the end of the file with a warning text. I did not add the new functionality in existing 'oslopolicy-policy-upgrade' tool because the above listed features of new tool end up creating a complete different code path instead of reusing it from existing tool so it better to have separate tool which can be removed in future once all deployments are migrated to YAML formatted file. This commits add doc and reno also for this tool Partial implement blueprint policy-json-to-yaml Change-Id: Icc245951b2992cc09a891516ffd14f3d4c009920
* Add oslopolicy-validator toolBen Nemec2020-06-261-0/+1
| | | | | | | | | | | | | | | | | | | | As requested in the referenced RFE bug, this is a validator tool similar to the oslo.config validator tool that operators can use to look for basic errors in their policy files. It's very similar to the redundant rule tool, but I decided not to combine them because I feel like the target use cases are enough different to warrant separate tools. Specifically, the redundant rule tool is looking for perfectly valid rules that just happen to be unnecessary. The validator is looking for errors in the policy file. While it's unlikely someone looking for redundant rules wouldn't also want to know if there is something broken in their policy file, it's likely that someone just looking to sanity check their policy before deployment wouldn't want to see a bunch of messages about redundant rules that won't cause any problems. Change-Id: I799a754aceac080c11baffd7ff635b2a9cb825f7 Closes-Bug: 1853038
* Remove translation sections from setup.cfgmelissaml2020-05-151-14/+0
| | | | | | | These translation sections are not needed anymore, Babel can generate translation files without them. Change-Id: I01d74cb5ff4701ca537dc3ec0f877b45cda7c895
* Add py38 package metadataSean McGinnis2020-04-241-0/+1
| | | | | | | | | Now that we are running the Victoria tests that include a voting py38, we can now add the Python 3.8 metadata to the package information to reflect that support. Change-Id: I602d143c89792824a2f206cdb45667b2f97e2e67 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
* [ussuri][goal] Drop python 2.7 support and testingHervé Beraud2020-02-061-21/+3
| | | | | | | | | | | | | | OpenStack is dropping the py2.7 support in Ussuri cycle. Complete discussion & schedule can be found in - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html - https://etherpad.openstack.org/p/drop-python2-support Ussuri Communtiy-wide goal: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html Change-Id: If6a07eee86a2aaf65bdf9fbb338809ad47e02a46
* Add Python 3 Train unit testsCorey Bryant2019-07-051-0/+1
| | | | | | | | | | | | 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 Change-Id: I64676b14b8a69d07e1b5fdc85e2a29523d4cf31d Story: #2005924 Task: #34234
* Dropping the py35 testingGhanshyam Mann2019-04-151-1/+1
| | | | | | | | | | | | | | | | | All the integration testing has been moved to Bionic now[1] and py3.5 is not tested runtime for Train or stable/stein[2]. As per below ML thread, we are good to drop the py35 testing now: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html [2] https://governance.openstack.org/tc/reference/runtimes/stein.html https://governance.openstack.org/tc/reference/runtimes/train.html Change-Id: Ic757ff7963f1dabd70610a884a4c61e747cd3961
* Add policy-upgrade toolwangxiyuan2018-12-111-0/+1
| | | | | | | | Add a new "oslopolicy-policy-upgrade" commnd. Using this command, operator can upgrade their self-defined policy files to follow the new format in the new release when upgrading OpenStack services. Change-Id: Iad9740bd8a5e4fdf1d1e64d61bc93f2483c531f3
* Change openstack-dev to openstack-discussZhongShengping2018-12-041-1/+1
| | | | | | Mailinglists have been updated. Openstack-discuss replaces openstack-dev. Change-Id: I84f738109f098415496619df423db7778b2fdcf2
* http/https check rules as stevedore extensionsDavanum Srinivas2017-10-051-0/+4
| | | | | | | | | | | | | | | | | Why? HttpCheck/HttpsCheck are examples of rule checks that can be implemented outside of the oslo.policy library. Once we setup the infra for registering and using these as stevedore extensions, we automatically get the capability of other folks contributing to writing custom rules for their own use cases. * Add HttpCheck/HttpsCheck as entrypoints in setup.cfg * parser will check get_extensions() to see if there are any external checks registered * Move HttpCheck/HttpsCheck into external module * Move related test cases to test_external.py Change-Id: Icde2b26a38d7c7842defae053228d9208454b969
* Update URLs in documents according to document migrationChangBo Guo(gcb)2017-07-121-1/+1
| | | | Change-Id: I7c9a0cef77d8564b8c6f0513da985b8ed0a404b9
* move existing documentation into new standard layoutDoug Hellmann2017-06-281-4/+5
| | | | | Change-Id: Iaefc26222d42663423f736946dea97c5613b7d1c Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Use Sphinx 1.5 warning-is-errorStephen Finucane2017-03-201-2/+5
| | | | | | | | | | With pbr 2.0 and Sphinx 1.5, the setting for treat sphinx warnings as errors is setting warning-is-error in build_sphinx section. Migrate the setting from the old warnerrors one. There are some invalid docstrings. These are cleaned up. Change-Id: Ic6a028bab428b23255f36e5b2d64ee8d4d32978d
* Remove references to Python 3.4ocata-em1.18.0Eric Brown2017-01-091-1/+0
| | | | | | | Now that there exists only a gate job for Python 3.5 and not 3.4, we should remove those references to the 3.4 that is untested. Change-Id: I1459093004581ea89c95e38a90f199ab4930d4ea
* Changed the home-page linkLuong Anh Tuan2016-10-111-1/+1
| | | | | | Set the correct url link for home-page Change-Id: I72da413012e2a967c4b7e0095b3452e7272fd19b
* Add Python 3.5 classifier and venvChangBo Guo(gcb)2016-07-121-0/+1
| | | | | | | | Now that there is a passing gate job, we can claim support for Python 3.5 in the classifier. This patch also adds the convenience py35 venv. Change-Id: I712c4e32e4db3e5ef826c69a11b8c3338753906f
* Fix mispelled method name in setup.cfgAndrew Laski2016-07-061-1/+1
| | | | | | | | The oslopolicy-policy-generator script was configured to use a method named genarate_policy. Unfortunately that method does not exist but there is one called generate_policy. This fixes the mistake. Change-Id: I04125bb3305f695e156e901543393abfae527a09
* Add helper scripts for generating policy infoAndrew Laski2016-06-081-0/+2
| | | | | | | | | | | | | | | | | | | This adds two helper scripts that consuming projects can use to get information that helps deployers. The oslopolicy-policy-generator script looks at an entry_point for a configured policy.Enforcer and outputs a yaml formatted policy file for that configuration. This is a merge of registered rules and configured rules. The oslopolicy_list_redundant script looks at an entry_point for a configured policy.Enforcer and outputs a yaml formatted policy file with a list of policies where the registered default matches the project configuration. These are policies that can be removed from the configuration file(s) without affecting policy. Change-Id: Ibe4e6c9288768bcc8f532e384524580c57e58275 Implements: bp policy-sample-generation
* Add sample file generation script and helper methods1.9.0Andrew Laski2016-06-061-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a console script to oslo.policy that will output a sample policy file in yaml format. It works by looking at the configured namespace(s) under an 'oslo.policy.policies' entry point. A method, or methods, should be provided which return a list of oslo_policy.policy.RuleDefault objects. To use this script add an entry to setup.cfg in a project with something like: oslo.policy.policies = nova.api = nova.api.opts:list_policies list_policies should be a method which returns a list of oslo_policy.policy.RuleDefault objects. Then run it like: oslopolicy-sample-generator --namespace nova.api --output-file can also be specified, or those options can be configured in a file which can be specified with --config-file. Change-Id: If25d48313b91a6610119220e13f635c6e28b2a59 Partially-Implements: bp policy-sample-generation
* Update translation setup1.4.0Andreas Jaeger2016-01-291-6/+6
| | | | | | | | | | | | | | | | | | | | Follow new infra setup for translations, see spec http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html for full details. This basically renames oslo.policy/locale/oslo.policy.pot to oslo_policy/locale/oslo_policy.pot. For this we need to update setup.cfg. Update also domain name in i18n.py. The project has no translations currently, let's remove the outdated pot file, the updated scripts work without them. So, we can just delete the file and once there are translations, an updated pot file together with translations can be imported automatically. Change-Id: I9ca723834b1634a9ed965a92724d72fefc15e0d2
* Add oslopolicy-checker command-line toolAdam Young2016-01-121-0/+5
| | | | | | | | | | | | | | | Allows testing the access_data from a Keystone token against all rules in a policy file. Optionally can test a single rule. See $ tox -e venv -- oslopolicy-checker --help For more details Co-Authored-By: Ian Cordasco <graffatcolmingov@gmail.com> Implements-Blueprint: oslopolicy-cli Change-Id: I8b2e8739c85077e856775f37e9868eb0a8babb3c
* Remove Python 2.6 classifierChangBo Guo(gcb)2015-11-171-1/+0
| | | | | | | | We have decided to remove Python 2.6 support, this commit removes Python 2.6 classifier before dropping any Python 2.6 support in code. Change-Id: I4de8aad0981f5af33964c1833410e79288938044
* Fixes up the API docs and module indexDavid Stanek2015-07-071-0/+1
| | | | | | | - Automatically generate the API docs - Makes the index on the modules index page useful Change-Id: I4eafe2c64a0733f6fb81b20e85cd943355860f9a
* Remove support for Python 3.3Davanum Srinivas2015-05-101-1/+0
| | | | Change-Id: Ibaac655357e822344661b32a33124a87351ccd2c
* Cleanup README.rst and setup.cfgSteve Martinelli2015-04-041-1/+1
| | | | | | | | | Provide a more complete description in README.rst, which is used when viewing the library on pypi. Also standardize the short-description used in setup.cfg. Change-Id: Ia3b56ba2abfc0c2826bff8e10f31e196d5c4031b
* Add entry points for option discoverySteve Martinelli2015-02-051-0/+4
| | | | | | | | Create entry points for oslo.policy, and make the necessary changes to grouping the options into a new 'oslo_policy' group. Change-Id: I32fd78c8a90fd2d49824db145362069b81fcaec5 Closes-Bug: #1415631
* Fix project metadataDoug Hellmann2015-01-281-2/+2
| | | | | | | Update the README and short description to fix links and be more descriptive. Change-Id: I8ff8130c66c35369d52ea59f9037cb32565518ae
* exported from oslo-incubator by graduate.shRodrigo Duarte Sousa2014-12-091-0/+53
View Lorry Controller Status