Exactly why AR System should not run as root :) On Wed, Nov 26, 2014 at 10:56 AM, Jarl Grøneng <[email protected]> wrote:
> ** > > echo ';rm -rf;' > > > -- > J > > 2014-11-26 16:33 GMT+01:00 John Sundberg <[email protected]>: > >> ** >> Gotta love that REST api. >> >> also YAY UNIX!!! >> >> BTW - can be pretty dangerous to put all that on the command line. >> >> You may want to write your data to a file. … Then post the data from the >> file. >> >> As — somebody could put in an RFE which would kick off your JIRA… >> Hopefully they don’t do something like >> >> Fix bug where people can do `echo “something bad here"` >> >> >> >> -John >> >> >> On Wed, Nov 26, 2014 at 7:21 AM, MalviyaSaurabh < >> [email protected]> wrote: >> >>> Hi All, >>> >>> This solved/ >>> >>> $PROCESS$ /opt/bcs/bin/curl -D- -k -u svc-remedy:password -X POST --data >>> “$Data1$” -H “Content-Type: application/json” >>> https://jiradev.company.com/rest/api/2/issue/ >>> >>> where DATA1 = as follows: >>> {"fields": >>> {"project": >>> { "id": "18168" }, >>> "summary":"Post-Mortem for Remedy *S3 - Major * Outage", >>> "description":"You have been identified as the post-mortem owner for >>> Remedy Ticket * 000000001714111 *. Please update this JIRA within 48 >>> hours >>> with the following information: </br> 1. Outage Summary - *scout >>> collector >>> heartbeat failure! scout collector may have stopped processing monitor >>> executions* </br> 2. Order of Events </br> 3. Root Cause and Resolution >>> </br> 4. Improvements Implemented </br> 5. Trends and Risks </br> 6. >>> Follow-Ups. </br> The NOC Debrief, within the Remedy ticket, is a >>> resource >>> you may use to populate some of this information. Additionally, you will >>> be >>> invited to participate in a post-mortem meeting. When you receive the >>> meeting invite, feel free to forward to others who were involved or >>> should >>> also attend. You will be requested to speak in detail to the areas listed >>> above.", >>> "reporter": >>> {"name": "repoterlogin"}, >>> "assignee": >>> {"name": "assigneelogin"}, >>> "issuetype": >>> { "id": "11000" } >>> } >>> } >>> >>> >>> >>> -- >>> View this message in context: >>> http://ars-action-request-system.1.n7.nabble.com/Creating-a-jira-issue-on-click-of-a-button-on-remedy-form-tp119290p119950.html >>> Sent from the ARS (Action Request System) mailing list archive at >>> Nabble.com. >>> >>> >>> _______________________________________________________________________________ >>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>> "Where the Answers Are, and have been for 20 years" >>> >> >> >> >> -- >> >> *John Sundberg* >> Kinetic Data, Inc. >> "Your Business. Your Process." >> >> 651-556-0930 I [email protected] >> www.kineticdata.com I community.kineticdata.com >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
