Global options

[Guy]

Hi all,

Is there any way to define global variables for a project, or even the level above that? I find I'm entering a lot of redundant data for each job.

Thanks,
Guy

[Greg Schueler]

Hi Guy,

No, not currently, but I like the idea. I assume you mean allow
additional ${key.name} expansion variables using values that you
somehow predefine?

I think someone has filed an issue in the tracker about adding this
kind of thing on a per-job basis, but per-project or global values
could be useful. This would help to make job definitions more like
templates, and allow your options and variable definitions fill in the
blanks.

Also, perhaps it should allow tying into an external sources
(pluggable), such as key-value stores?

[Guy Knights]

Hi Greg,

Well I've only just delved into the world of rundeck so all I know so far is defining an option in a job and accessing it via ${option.<key name>}. I think that's what you were referring to in your first paragraph below, is that right? If so, then yes, I was talking about defining these types of options at the project level instead, so you can access them across multiple jobs.

At the moment my focus has purely been on defining options locally, not pulling them from external sources (except for node definitions) but sure, being able to draw them from external sources would probably be useful as well.

Also, while I'm on the subject of project level options, it would be nice if you could use named filters from the "Run" page as node options within jobs. I brought this up in another thread on this mailing list but thought it was worth mentioning here as well.

So far I'm liking rundeck a lot, I look forward to getting better acquainted with it!

Thanks,
Guy

--
Guy Knights
Systems Administrator
Eastside Games
www.eastsidegamestudio.com
g...@eastsidegamestudio.com

[Hasan]

That gets my vote  +1

Yes, please . . . ASAP

On Thursday, May 31, 2012 7:28:05 PM UTC-5, Guy wrote:

Hi Greg,

Well I've only just delved into the world of rundeck so all I know so far is defining an option in a job and accessing it via ${option.<key name>}. I think that's what you were referring to in your first paragraph below, is that right? If so, then yes, I was talking about defining these types of options at the project level instead, so you can access them across multiple jobs.

At the moment my focus has purely been on defining options locally, not pulling them from external sources (except for node definitions) but sure, being able to draw them from external sources would probably be useful as well.

Also, while I'm on the subject of project level options, it would be nice if you could use named filters from the "Run" page as node options within jobs. I brought this up in another thread on this mailing list but thought it was worth mentioning here as well.

So far I'm liking rundeck a lot, I look forward to getting better acquainted with it!

Thanks,
Guy

On Thu, May 31, 2012 at 5:14 PM, Greg Schueler wrote:

Hi Guy,

No, not currently, but I like the idea.  I assume you mean allow
additional ${key.name} expansion variables using values that you
somehow predefine?

I think someone has filed an issue in the tracker about adding this
kind of thing on a per-job basis, but per-project or global values
could be useful. This would help to make job definitions more like
templates, and allow your options and variable definitions fill in the
blanks.

Also, perhaps it should allow tying into an external sources
(pluggable), such as key-value stores?

[robert...@gmail.com]

Hi,

 

have there been any advances in providing options for project wide variables? It would be very useful to be able to define variables either globally for all projects within Rundeck, or even at the project level, where multiple jobs can leverage the same piece of configuration. We have a lot of jobs that use certain directory paths that change over time, and having to manually update large number of jobs across several projects is a bit tedious.

 

Or if the configuration xml for the job could be stored outside of the database, this could also be easily accomplished with config management tools. I understand jobs can be exported, modified, then re-imported, so that could be a workaround. Global variables though would definitely be helpful. Thanks for a great product.

 

Thanks,

Robert.

[Greg Schueler]

Hi Robert,

We haven't implemented this yet, but it is on the short todo-list for upcoming releases.

--
Greg Schueler

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Adrian Howchin]

Hi Greg,

Did this make it into 2.4.1 by any chance?

Cheers,

Adrian

[Greg Schueler]

HI Adrian,

this feature is not implemented yet, sorry

-- 
Greg Schueler

[Jojo]

Hi,

Is it still on the todo list ?

[Juan Carlos Rueda Fernández]

Hi support team,

has this interesting featured developed?

Is there any workaround?

We are using some jobs as templates and use them in other projects. We want to define some global options/variables at project level and use them in job references.

Thanks.

[Reiner Acuña]

Hi Juan,

You can define global variables following this:

https://docs.rundeck.com/docs/administration/configuration/config-file-reference.html#global-execution-variables

Regards!

[Reiner Acuña]

Also, you can check this example of passing data between jobs using Job reference step (even between projects), take a look:

https://stackoverflow.com/a/61802154/10426011

Regards!

On Wednesday, May 27, 2020 at 4:03:53 PM UTC-4, Juan Carlos Rueda Fernández wrote:

[Juan Carlos R]

Hi Reiner,

thank you for this information. It will be useful.

I was searching some way to create some common options in the project scope using GUI. Using GUI, administrators could create them without properties file access.

I will review global variables.

Regards,

[Reiner Acuña]

Hi Juan,

In that case, you can use the Global Variable. Create or edit your job, go to the Workflow Step tab, and select "Global Variable", I leave an example, feel free to modify it:

<joblist>
  <job>
    <defaultTab>nodes</defaultTab>
    <description></description>
    <executionEnabled>true</executionEnabled>
    <id>41c33de6-f9dc-449e-aa01-c7c6083e21d2</id>
    <loglevel>INFO</loglevel>
    <name>JobEXAMPLE</name>
    <nodeFilterEditable>false</nodeFilterEditable>
    <plugins />
    <scheduleEnabled>true</scheduleEnabled>
    <sequence keepgoing='false' strategy='node-first'>
      <command>
        <step-plugin type='export-var'>
          <configuration>
            <entry key='export' value='myglobal' />
            <entry key='group' value='export' />
            <entry key='value' value='hello' />
          </configuration>
        </step-plugin>
      </command>
      <command>
        <exec>echo ${export.myglobal}</exec>
      </command>
    </sequence>
    <uuid>41c33de6-f9dc-449e-aa01-c7c6083e21d2</uuid>
  </job>
</joblist>

Of course, you can pass that variable between jobs/projects using job reference step like this example: https://groups.google.com/d/msg/rundeck-discuss/h6XAdkyNWO8/j0_alNZQEQAJ

Hope it helps!