I'm using Swagger UI to create the docs for a custom REST API.
I disabled the "Try it out" button since I don't want it, but I would love to show the curl command of every request.
Is there a way to show it without activating the "try it out" button? Or maybe add something in the YAML file that shows one more div with custom text in it?
Is there a way to show it without activating the "try it out" button?
No. Swagger UI's curl command generator depends on "try it out" availability, because the commands are generated based on the specific parameter values that the user specified during "try it out".
Or maybe add something in the YAML file that shows one more div with custom text in it?
You can add use the description field of operations to add details, such as code examples. Descriptions support Markdown for rich text formatting.
paths:
/something:
get:
summary: Get something
description: >-
Detailed description goes here.
And here's some code:
curl https://example.com/something -H "Accept: application/json"
responses:
200:
description: Successful response
Related
I intermittently run into a TYPE_021 error when I perform a 'Set Text' action on a web-element that would be used as a drop-down in a manual flow, but simply inputting a value is legal.
I chose a 'Set Text' versus a Click command followed by a Keystrokes command because 'Set Text' seems more stable. Also, I did not attempt the obvious flow of selecting from the dropdown because the necessary value is not available in the dropdown.
What would cause a TYPE_021 error?
I agree with the availability of user guides for Automation Anywhere.. which is frustrating. I'm also not familiar with those type of errors but I would suggest the following methods:
Enclose Set Text command with Error Handling so that the whole task would not fail if the drop-down value is not available, then have If/Else commands after to check if it is valid or not.
Error Handling (Action: Continue; Task Status: Pass; Variable Operation = "True")
Move the drop-down selection part at the latter part of the task. Maybe the page was not fully loaded yet which causes failure.
Use Click command to select the value. Click the drop-down button then click the value. Modify the properties to insert the value required, maybe on HTML Value or HTML InnerText. You may enclose it with Error Handling if needed.
I'm using hubot with the hubot-slack adapter.
I have a very long url that I'd like to write to the chatroom, and would like to display it as a link.
From this:
http://magnum-ci.oak.domain.com:8080/job/nick_test_success_build/44/console
To this:
Click here to view the console out
I'm using:
res.send "http://magnum-ci.oak.domain.com:8080/job/nick_test_success_build/44/console|link"
I haven't tried this recently with Hubot, but note that it doesn't work as a user.
Slack's docs make it look like you can use "labels" to display friendly URL names. See the last example on this page https://api.slack.com/docs/unfurling
You may be able to send the text
<http://mylink.com|Show this>
in a message and get the desired results.
I tried this a long time ago and don't remember if it worked.
#mshish is right, <http://mylink.com|Show this> should be the way to go.
You can test the output of your link using the Message Builder.
Unfortunately it looks like this is not currently supported by the hubot.
https://github.com/slackhq/hubot-slack/issues/114
I would like to be able to add a flag to an issue via the Jira API. I was unable to find any documentation regarding this issue. Does anyone know how this works?
I've figured out how to do this, I'm not sure on the version of the API. I made a POST request to:
yourdomain /rest/greenhopper/1.0/xboard/issue/flag/flag.json
And in the body (replace JIRA-ISSUE with your issue key):
{"issueKeys":["JIRA-ISSUE"],"flag":true}
I hope this helps.
Here is the best answer I found.
https://answers.atlassian.com/questions/38062844/answers/38062897
There is a field called Flagged. It is a checkbox type field. There is a single value by default, Impediment. The field is checked for null status. If the field is null, the issue is not flagged. If the field is not null, the issue is flagged.
You would use the REST API for this. Examples are here –
https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-create-issue.
You'll either need to know the field ID (customfield_10000) or you need to to script the discovery of the field by searching the metadata – https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-discovering-meta-data-for-creating-issues.
An example of setting a custom field while creating the issue over API –
curl -D- -u fred:fred -X POST --data {"fields":{"project":{"key": "TEST"}, "summary": "Always do right. This will gratify some people and astonish the REST.", "description": "Creating an issue while setting custom field values", "issuetype":{"name": "Bug"}, "customfield_10000": [{"value": "Impediment"}]}} -H "Content-Type: application/json" http://localhost:8090/rest/api/2/issue/
non-minified data Expand source
{
"fields": {
"project":
{
"key": "TEST"
},
"summary": "Always do right. This will gratify some people and astonish the REST.",
"description": "Creating an issue while setting custom field values",
"issuetype": {
"name": "Bug"
},
"customfield_10000": [ {"value": "Impediment" }]
}
}
As mentioned here, "Flagged" is a checkbox custom field that accepts a single value "Impediment".
You should be able to set it using the JIRA REST API just like any other custom field. Maybe the examples here will help.
You can also set custom field values using the JIRA Java API.
I'm struggling with this right now. It seems that the Flagged field is not a checkbox type field anymore, but multicheckbox. So the data format I need to send to Jira Cloud API to set the flag in my case look like this:
{update:
{customfield_10021:
[{set:
[{id:“10019”}]
}]
}
}
To remove the flag the data I sent to Jira look like this:
{update:
{customfield_10021:
[{set:
[]
}]
}
}
In the above customfield_10021 is Flagged field's key and 10019 is id that sets the flag. Both of them you need to figure out for your Jira Cloud instance for example by aquiring issue with set Flagged field and checking how it is set.
Just to make it clear, to add/remove a flag I use edit issue end point described here.
Also, to be able to add/remove flag the Flagged field has to be on the edit screen of the issue type that you want to modify and your user needs to have proper priviliges.
I'm using the Google Analytics Google Spreadsheets plugin.
I'd like to segment data to only include visitors who have an event action of "get started" against them.
Here is what I tried when I try to run the report Google Sheets says the syntax is invalid:
segment=users::condition::ga:eventAction=#started
Then tried:
segment=users::condition::ga:eventAction==get started
Then tried:
segment=users::condition::ga:eventAction=="get started"
How do I tell the Google-Analytics API to return only users who have triggered the event action "get started"?
I'm not sure if I'm close or not. I suspect it might have something to do with the space between "get" and "started". But if that was the case maybe the attempt using =# would have worked?
I believe your first example will work once you remove the "segment=" part of the string.
i want to create an issue in JIRA by using the REST API provided by JIRA.
i am able to create a simple issue,
using this :
http://localhost:8080/rest/api/latest/issue
and data as follows:
{"fields":{"project":{"key": "TES"},"summary":"user name not showing validation message","description":"Hi validation is missing from user name","issuetype": {"name": "Bug"},"reporter":{"name":"BruceWayne"} }}
this is running fine.
now i want to add 3 custom fields while creating an issue. The custom fields are Authorname,
AuthorTag,AuthorID. how can i do this in rest api. what should i add in my data.
My sample data is as follows:-
{"fields":{"project":{"key": "TES"},"summary":"my bugs 5","description":"Hi","issuetype": {"name": "Bug"},
"customfield_10000":"roach#yahoo.com",
"customfield_10100":{"value":"abc"},
"reporter":{"name":"amit"},
"components": [{
"add" : {"name" : "abc"}
}],"priority": {
"id": "1"
}
}}
i want to use the names specified for customfields rather than customfield_XXXXX .
One way i think of is to hit the API after creating a simple issue ( using another API hit to get meta data as follows)
http://localhost:8080/rest/api/latest/issue/tes-79?expand=editmeta
and then do json parsing and again issue a put command to update the fields in same issue
but i was looking for a way to do it in single API hit (while creating an issue)
It should be just like setting any other field, but you have to use the field name "customfield_NNNNN" instead
I know that it is very late to answer this question, but then might help others if not the OP at this time of writing.
If you're in doubt about the create, then you could do something like this - Try a GET on an issue that you would rather create manually with the new parameters as well and then based on the output of the same you could then decide to update it with the new parameters with the new name or the old-fashioned customfield_xxx field.
Try a GET like this on cURL
curl -D- -u fred:fred -X GET -H "Content-Type: application/json" https://jira.fred.com/rest/api/2/issue/FRD-88651
Then you could possibly do a POST like how you've done earlier:
http://localhost:8080/rest/api/latest/issue