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

Use options in remote URL? #1

Open
willemdh opened this issue Jul 1, 2016 · 6 comments
Open

Use options in remote URL? #1

willemdh opened this issue Jul 1, 2016 · 6 comments

Comments

@willemdh
Copy link

willemdh commented Jul 1, 2016

Hello,

Is it possible to use options in the remote URL?

For example:
https://@option.nagiosserver@/nagiosxi/api/v1/system/applyconfig&apikey=${option.nagiosapikey}&pretty=1

results in Execution failed: 61: [Workflow result: , step failures: {2=HTTPFailure: Error when sending request: option.nagiosserver@}

I could of course use curl in a bash script, but it should be working in the HTTP plugin no?

Thanks and grtz

@ikogan
Copy link
Collaborator

ikogan commented Jul 6, 2016

This is certainly on the agenda but since we don't use this kind of functionality currently, I can't give any sort of estimate as to when it might be implemented. A PR would certainly be welcome though!

@willemdh
Copy link
Author

willemdh commented Jul 6, 2016

I'm not so good at Java though, so I will not be able to give you a pr. I'll stick with using curl for now. Thanks for the info!

@fellenberger
Copy link

Hello, just a quick ping on this thread. Any idea on when this can be implemented? Supporting the use of rundeck job variables/options would greatly enhance the usefulness of this already very cool plugin. That being said, we are most certainly going to give it a go without this enhancement in place.

Hoping there would be java-based examples that can be referenced from other plugin projects to button this feature request up with minimal coding effort (for a java developer that is...).

Thanks for sharing this plugin!

ltamaster pushed a commit to rundeck-plugins/http-step that referenced this issue Mar 22, 2017
+ Pass headers using JSON or YML format (ohioit#3)
+ Pass body text
+ Print the response on rundeck
+ Print the response to a file
+ Move the authentication fields to the job level
+ getting the authentication  password from the key storage
+ Use options in remote URL  (ohioit#1)
@ieugen
Copy link

ieugen commented Oct 25, 2017

We need to supply password in options remote URL because this is the only way we can access private data on a sonatype nexus server.

I'm using rundeck 2.10.x and substiturion in remote url of Option does not work.

@ikogan
Copy link
Collaborator

ikogan commented Oct 25, 2017

Substitution of options, generally, is not implemented. While obviously not desirable, have you tried putting username:password into your URL? https://username:password@yourdomain/path.

This is obviously problematic as this password won't be scrubbed anywhere, including in logs.

@ikogan
Copy link
Collaborator

ikogan commented Jul 22, 2020

Hey, thank you for your suggestion! Unfortunately we aren't able to maintain the project anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants