@itentialopensource/adapter-paragon_active_assurance 0.1.2 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (49) hide show
  1. package/.eslintignore +0 -1
  2. package/.jshintrc +3 -0
  3. package/CALLS.md +175 -139
  4. package/CHANGELOG.md +8 -0
  5. package/CONTRIBUTING.md +1 -160
  6. package/ENHANCE.md +2 -2
  7. package/README.md +31 -22
  8. package/adapter.js +163 -334
  9. package/adapterBase.js +538 -873
  10. package/changelogs/CHANGELOG.md +16 -0
  11. package/metadata.json +51 -0
  12. package/package.json +24 -26
  13. package/pronghorn.json +474 -142
  14. package/propertiesSchema.json +452 -40
  15. package/refs?service=git-upload-pack +0 -0
  16. package/report/adapter-openapi.json +15052 -0
  17. package/report/adapter-openapi.yaml +10325 -0
  18. package/report/adapterInfo.json +8 -8
  19. package/report/updateReport1691508876405.json +120 -0
  20. package/report/updateReport1692202191653.json +120 -0
  21. package/report/updateReport1692203293320.json +120 -0
  22. package/report/updateReport1694469109205.json +120 -0
  23. package/report/updateReport1698422878147.json +120 -0
  24. package/sampleProperties.json +67 -14
  25. package/test/integration/adapterTestBasicGet.js +1 -1
  26. package/test/integration/adapterTestConnectivity.js +91 -42
  27. package/test/integration/adapterTestIntegration.js +130 -2
  28. package/test/unit/adapterBaseTestUnit.js +388 -315
  29. package/test/unit/adapterTestUnit.js +307 -110
  30. package/utils/adapterInfo.js +1 -1
  31. package/utils/addAuth.js +1 -1
  32. package/utils/artifactize.js +1 -1
  33. package/utils/checkMigrate.js +1 -1
  34. package/utils/entitiesToDB.js +1 -0
  35. package/utils/findPath.js +1 -1
  36. package/utils/methodDocumentor.js +71 -23
  37. package/utils/modify.js +13 -15
  38. package/utils/packModificationScript.js +1 -1
  39. package/utils/taskMover.js +309 -0
  40. package/utils/tbScript.js +3 -10
  41. package/utils/tbUtils.js +2 -3
  42. package/utils/testRunner.js +1 -1
  43. package/utils/troubleshootingAdapter.js +1 -3
  44. package/.gitlab/.gitkeep +0 -0
  45. package/.gitlab/issue_templates/.gitkeep +0 -0
  46. package/.gitlab/issue_templates/Default.md +0 -17
  47. package/.gitlab/issue_templates/bugReportTemplate.md +0 -76
  48. package/.gitlab/issue_templates/featureRequestTemplate.md +0 -14
  49. package/workflows/README.md +0 -3
@@ -1,76 +0,0 @@
1
- # Bug Report
2
-
3
- Thanks for taking the time to fill out this bug report!
4
-
5
- Before creating bug reports, please check before-submitting-a-bug-report, as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible.
6
-
7
- #### Before Submitting A Bug Report
8
-
9
- * **Check the README.md.** You might be able to find the cause of the problem and fix things yourself. Most importantly, check if you can reproduce the problem __in the latest version__.
10
- * **Work through the troubleshooting process.** Troubleshooting will include changing the log level of Itential Automation Platform (IAP) and adapters and checking the logs to see what the issues are. These logs should be included in any ticket you open for this issue.
11
- * **Check for resolutions to the issue.** Check the <a href="https://itential.atlassian.net/servicedesk/customer/kb/view/286883841?applicationId=605994d2-2cb2-3174-af59-ed5b23ff5fd5&spaceKey=PKB&src=1187380921" target="_blank">Itential Knowledge Base</a> to see if there is a known resolution for the issue you are having.
12
- * **Ask around in chat if you are an Itential employee** to see if others are experiencing the same issue.
13
-
14
- #### How to Submit a (Good) Bug Report
15
-
16
- Please read the guidlines and move to describe-the-bug. Explain the problem and include additional details to help maintainers reproduce the problem:
17
-
18
- - **Use a clear and descriptive title** for the issue to identify the problem.
19
- - **Describe the exact steps which reproduce the problem** in as much detail as possible. For example, start by explaining how you configured the adapter (e.g., which properties you used and how they were set) or how you are using an artifact.
20
- - **Provide specific examples to demonstrate the steps**. Include logs, or copy/paste snippets, in your examples.
21
- - **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
22
- - **Explain which behavior you expected to see instead and why.**
23
- - **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem. You can use <a href="https://www.cockos.com/licecap/" target="_blank">this tool</a> to record GIFs on macOS and Windows. Use <a href="https://github.com/colinkeenan/silentcast" target="_blank">this tool</a> or <a href="https://github.com/rhcarvalho/byzanz-guiz" target="_blank">program</a> on Linux.
24
- - **If the problem wasn't triggered by a specific action**, describe what you were doing before the problem happened and share more information using the guidelines below.
25
-
26
- Provide more context by answering these questions:
27
-
28
- - **Did the problem start happening recently** (e.g. after updating to a new version/tag) or was this always a problem?
29
- - If the problem started happening recently, **can you reproduce the problem in an older version/tag?** What's the most recent version in which the problem does not happen?
30
- - **Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
31
-
32
- Include details about your configuration and environment:
33
-
34
- - **Which version of the adapter/artifact are you using?** You can get the exact version by checking the project version in the package.json file.
35
- - **What's the name and version of the OS you're using**?
36
- - **Are you running or using IAP in a virtual machine?** If so, which VM software are you using and which operating systems and versions are used for the host and guest?
37
- - **Are there firewalls between IAP and any other system you are integrating with?** If so, have you tried running curl from the system IAP is on to the other system to verify you have connectivity between the systems?
38
-
39
- ## Describe the bug
40
-
41
- _[A clear and concise description of what the bug is.]_
42
-
43
- ## IAP Version
44
-
45
- _[List the IAP Version that the bug is happening in.]_
46
-
47
- ## NPM Package version
48
-
49
- _[List the npm package version.]_
50
-
51
- ## Steps To Reproduce
52
-
53
- _[List out the exact steps to reproduce the issue here.]_
54
-
55
- ### Expected behavior
56
-
57
- _[A clear and concise description of what you expected to happen.]_
58
-
59
- ### Current behavior
60
-
61
- _[List out the current behavior here.]_
62
-
63
- ### Screenshots/Video
64
-
65
- _[If applicable, add screenshots/video to help explain or demo the issue here.]_
66
-
67
- ## Possible fixes
68
-
69
- _[If you can, link to the line of code that might be responsible for the problem.]_
70
-
71
- ## Additional context
72
-
73
- _[Add any other context about the problem here.]_
74
-
75
- /label ~"Issue Type::Bug"
76
- /assign @ishita.prakash
@@ -1,14 +0,0 @@
1
- <!-- markdownlint-disable MD036 -->
2
-
3
- # Feature Request
4
-
5
- ## Describe the new feature
6
-
7
- _[A clear and concise description of what changes you would like to see.]_
8
-
9
- ## Possible Solutions
10
-
11
- _[List out possible suggestions on how to add this feature if you have any.]_
12
-
13
- /label ~"Issue Type::Feature Request"
14
- /assign @ishita.prakash
@@ -1,3 +0,0 @@
1
- # Adapter Workflows
2
-
3
- This directory contains workflows that support the adapter use cases. These workflows can be imported into IAP. If the adapter is installed using App-Artifact the workflows should be automatically imported.