f9981c0825
Subscription wizard SUMMARY Adds subscriptions routes Extends Config context to return an array with two items: config state and config setter Update components that use Config with the new return pattern Move mock config into setupTests.js Return only the routes the user is "authorized" (valid license key) to view Subscription Details view: /settings/subscription/details This is our standard details view Clicking Edit will send the user to subscription wizard view /settings/subscription/edit Route is not accessible when license type is OPEN Subscription Add wizard view: /settings/subscription_management Step 1 - Subscription: If a user does not have a Red Hat Ansible Automation Platform subscription, they can request a trial subscription via the link Toggle between uploading a subscription manifest .zip file or retrieving subscriptions using Red Hat credentials (username and password) Get Subscriptions button fetches subscriptions and displays them in a modal Step 2 - Tracking and analytics: Shows two checkboxes to enable User analytics and Automation analytics If the user has previously selected the RH subscription manifest flow, checking the Automation Analytics box will display required RH username and password fields If the user has previously selected the RH username/password flow, they will not see this additional username/password field if Automation Analytics is checked Step 3 - EULA: https://tower-mockups.testing.ansible.com/patternfly/settings/settings-license-step-03/ Submission should show a success message and navigate user to dashboard if this is the initial launch and to the subscription detail view if they are editing the subscription Failed submission should show a wizard form error ISSUE TYPE Feature COMPONENT NAME UI ADDITIONAL INFORMATION Reviewed-by: Michael Abashian <None> Reviewed-by: Kersom <None> Reviewed-by: Tiago Góes <tiago.goes2009@gmail.com>
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is the upstream project for Tower, a commercial derivative of AWX.
To install AWX, please view the Install guide.
To learn more about using AWX, and Tower, view the Tower 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 --signoff for any commit to be merged and agree that usage of --signoff constitutes 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 the
#ansible-awxchannel on webchat.freenode.net and talk about what you would like to do or add first. This not only helps everyone know what's going on, but 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 ask 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. Here's how to reach us with feedback and questions:
- Join the
#ansible-awxchannel on webchat.freenode.net - Join the mailing list