Pratyush BhandariandPeter Braun
32f588e15b
* feat(api): advertise validation patterns on JSON sub-key fields Credential type inputs.fields/metadata and notification OPTIONS now include pattern and pattern_description for non-secret string sub-keys when ENHANCED_INPUT_VALIDATION_ENABLED is on. * Fix lint issue * Fix sonarqube issue * feat(api): advertise validation patterns on top-level CharFields Wires DAB's inject_clean_text_patterns into awx.api.metadata.Metadata so top-level CharField OPTIONS metadata gets pattern/patternDescription/flags, matching the JSON sub-key pattern exposure already in place. No-op until ENHANCED_INPUT_VALIDATION_ENABLED is on and a serializer mixes in CleanTextMixin. Signed-off-by: Pratyush Bhandari <prbhanda@redhat.com> * Increase test coverage * Fix lint issues * Address review feedback on validation pattern injection Import TIER2_PATTERN_DESCRIPTION from DAB instead of keeping a manually synced duplicate, and short-circuit inject_patterns_into_field_list before iterating fields when enhanced input validation is disabled. Signed-off-by: Pratyush Bhandari <prbhanda@redhat.com> * Avoid mutating shared field dicts in inject_patterns_into_field_list Shallow-copy each field before injecting pattern metadata so callers that pass module-level schema dicts (e.g. ManagedCredentialType.registry entries) don't get them mutated in place, matching the existing copy-before-mutate approach in inject_patterns_into_init_parameters. Signed-off-by: Pratyush Bhandari <prbhanda@redhat.com> * Add validation pattern for survey fields --------- Signed-off-by: Pratyush Bhandari <prbhanda@redhat.com> Co-authored-by: Peter Braun <pbraun@redhat.com>
Caution
The last release of this repository was released on Jul 2, 2024. Releases of this project are now paused during a large scale refactoring. For more information, follow the Forum and - more specifically - see the various communications on the matter:
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
To install AWX, please view the Install guide.
To learn more about using AWX, view the AWX docs site.
The AWX Project Frequently Asked Questions can be found here.
The AWX logos and branding assets are covered by our trademark guidelines.
Contributing
- Refer to the Contributing guide to get started developing, testing, and building AWX.
- All code submissions are made through pull requests against the
develbranch. - All contributors must use
git commit --signofffor any commit to be merged and agree that usage of--signoffconstitutes agreement with the terms of DCO 1.1 - Take care to make sure no merge commits are in the submission, and use
git rebasevs.git mergefor this reason. - If submitting a large code change, it's a good idea to join discuss via the Ansible Forum. This helps everyone know what's going on, and it also helps save time and effort if the community decides some changes are needed.
Reporting Issues
If you're experiencing a problem that you feel is a bug in AWX or have ideas for improving AWX, we encourage you to open an issue and share your feedback. But before opening a new issue, we ask that you please take a look at our Issues guide.
Code of Conduct
We require all of our community members and contributors to adhere to the Ansible code of conduct. If you have questions or need assistance, please reach out to our community team at codeofconduct@ansible.com
Get Involved
We welcome your feedback and ideas via the Ansible Forum.
For a full list of all the ways to talk with the Ansible Community, see the AWX Communication guide.