- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus Enterprise Software
- >
- Re: Hide Task Output but use the value in another ...
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2024 02:48 PM
03-13-2024 02:48 PM
I need to retrieve a sensitive information from a remote endpoint using Rest API calls. But I don’t want this information to be displayed on the Task Output. But I want that output value to another task. Also I dont want to merge this two task because that first task needs to be reused for multiple other tasks. Please advise.
Solved! Go to Solution.
- Tags:
- automation
- cypher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 04:26 AM
03-14-2024 04:26 AM
Re: Hide Task Output but use the value in another Task
The best option is probably writing the value to cypher in the first script. Then you could either have a task clean up the cypher, or just each run pulls the latest value and the cypher value.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2024 09:10 PM
03-18-2024 09:10 PM
Re: Hide Task Output but use the value in another Task
(post deleted by author)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2024 09:01 AM
03-17-2024 09:01 AM
Re: Hide Task Output but use the value in another Task
Very good idea. Depending on how often this task is executed and how long the respective information remains relevant, the Cypher entry could also be designed accordingly. The task ID, the instance name or similar could be used in the name. In addition, a separate mount point could be created for clarity.
<%= cypher.read("secret\MountPointName" + results.blah) %>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 07:54 AM
03-14-2024 07:54 AM
Re: Hide Task Output but use the value in another Task
Even though this is good option, the issue will be that there could be users running the task at the same time which may collide with the Cypher variable.
Anyhow, Could you please provide some examples to update the Cypher directly. Anyhow, I know there is an option using the API.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 08:19 AM
03-14-2024 08:19 AM
SolutionI would take a look at generating a cypher with a randomly generated name. Pass that as the output of your results. Then the following calls could use something like
<%= cypher.read("secret\" + results.blah) %>
Cypher API docs can be found here.
If you have further issues or require demonstration of this flow, I would recommend opening a Technical Request at https://support.morpheusdata.com