Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Automate update of the resources file from the URL

#259

As things stand updating the resources file from the resource provider URL is manually triggered from the web UI.

While there is a ticket in the system to provide a programable trigger for this process via the web API (#250 WebAPI to update project resources file) ... there is also a case for letting the resources URL take precedence over the file and thereby completely eliminate the need for any update process.

In other words perhaps Rundeck's access to the resource model should be solely via a web based interface, or if the design requires the existence of a local resource file then that file be automatically updated from the URL each time a job is run (if configured to do so).

Reported by Anthony Shortland · April 21st, 2011 @ 03:23 PM

State: stalled
Milestone: none
Assigned to: nobody

Activity

  1. Deleted User
    Deleted User

    What would the expected behavior be if:

    • The resource is slow to generate, say in the minutes on each request
    • The resource is not available either due to remote server error or network hiccup

    April 21st, 2011 @ 09:05 PM

  2. Greg Schueler
    Greg Schueler

    April 27th, 2011 @ 01:32 PM

  3. Greg Schueler
    Greg Schueler
    • State changed from new to hold

    nb: rundeck 1.4 URL resource model source will auto-retrieve the contents

    October 28th, 2011 @ 12:24 PM

  4. Greg Schueler
    Greg Schueler
    • State changed from hold to stalled

    June 22nd, 2012 @ 10:46 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.