Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the policy create UI/UX by preprocessing the policy definition file to autofill policy attribute details #12560

Open
ashera96 opened this issue Mar 6, 2022 · 0 comments
Labels

Comments

@ashera96
Copy link
Contributor

ashera96 commented Mar 6, 2022

Describe your problem(s)

As per the Operation Level Policy Support feature introduced with APIM 4.1.0 release, users have to manually type in the policy attribute names (and corresponding details) in the policy create form. We can automate this to some extent in order to minimize redundant work and typos so as to avoid any unexpected behaviour later on. Upon policy definition file upload (.j2 or .xml for Synapse gateway related uploads and .gotmpl for Choreo Connect gateway related uploads), we can parse the uploaded file(s) to deduce and autofill policy attribute details.

Describe your solution

Do a REST API call on file upload to get the policy attribute details in order to auto populate the form. This way, we can make those autofilled fields read-only. Thus, we can remove any redundant work on the users' part and eliminate any unexpected behaviours from the backend or when invoking the API.

How will you implement it

  • REST API call to parse the policy definition file
  • Using the response of that call, populate the UI rather than letting the user type it in
@ashera96 ashera96 added Type/Improvement Priority/Normal Feature/OperationPolicies Operation policies feature related issues labels Mar 6, 2022
@tharikaGitHub tharikaGitHub added the APIM - 4.1.0 APIM manager 4.1.0 release related issues. label Mar 9, 2022
@Krishanx92 Krishanx92 added 4.x.x and removed APIM - 4.1.0 APIM manager 4.1.0 release related issues. labels Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants