b336400963
* Add PostgreSQL utility functions for metrics-utility Creates two plpgsql functions used by metrics-utility when querying the AWX controller database via a read-only connection: - metrics_utility_parse_yaml_field: extracts a named field from YAML-encoded text - metrics_utility_is_valid_json: validates whether a text value is valid JSON GRANT EXECUTE TO PUBLIC so any database user (including ms_awx_readonly) can call the functions without requiring an explicit per-user grant. The migration is a no-op on SQLite so unit and functional tests are unaffected. Assisted-by: Claude Code (claude-sonnet-4-6) Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ciaran Shiels <cas.ireland@Gmail.com> * Fix regex injection and broad exception in metrics utility migration - Escape `field` parameter before interpolating into regex pattern using regexp_replace with the whole-match `&` reference rather than bare concatenation; prevents regex metacharacters in the field name from altering match semantics - Narrow `EXCEPTION WHEN others` to `WHEN invalid_text_representation` (SQLSTATE 22P02) in metrics_utility_is_valid_json so only the expected JSON-cast failure is swallowed and unexpected runtime errors propagate Assisted-by: Claude Code (claude-sonnet-4-6) Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ciaran Shiels <cshiels@redhat.com> * Renumber migration 0206 to 0210 to avoid conflict Re-parent create_metrics_utility_functions migration from 0205 to 0209 after other migrations (0206–0209) merged to devel since branch creation. Co-authored-by: Cursor <cursoragent@cursor.com> * Renumber migration 0210 to 0211 to avoid conflict 0210_remove_host_last_job_fields arrived on devel after the last rebase, re-parent create_metrics_utility_functions to depend on it instead. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Signed-off-by: Ciaran Shiels <cas.ireland@Gmail.com> Signed-off-by: Ciaran Shiels <cshiels@redhat.com> Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.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.