nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Parameterize excludes?

croot

Hello -

I'm building an workflow external task that reads in a configuration file and then calls an opendeploy script based on parameters retrieved from the file. The idea is to have the script pass along the following three things:

1. Source area
2. Target area
3. Excludes

I am struggling with the excludes as there can be more than one in the configuration file. When I pass along something like this:

iwodcmd start od_script.xml -k srcarea=Y:\default\main\awards\STAGING -k target=/app/htdocs/awards -k exclude="‹excludePath subPath='ex.html' />‹excludePath subPath='ex2.html' />"

the files are not excluded from the deployment. It doesn't seem to like the "<" or ">". The exclude portion of my deployment script looks like this:

‹fileSystem area="$srcarea^" filelist="" >
‹remoteDiff area="$srcarea^">
‹pathSpecification >
‹path name="." />
‹filters>
$exclude^
‹/filters>
‹/pathSpecification>
‹/remoteDiff>
‹/fileSystem>

Has anyone done anything like this before and been successful?

Thanks,
Chris

Find more posts tagged with

Comments

Adam Stoller

Hello -

I'm building an workflow external task that reads in a configuration file and then calls an opendeploy script based on parameters retrieved from the file. The idea is to have the script pass along the following three things:

1. Source area
2. Target area
3. Excludes

I am struggling with the excludes as there can be more than one in the configuration file. When I pass along something like this:

iwodcmd start od_script.xml -k srcarea=Y:\default\main\awards\STAGING -k target=/app/htdocs/awards -k exclude="‹excludePath subPath='ex.html' />‹excludePath subPath='ex2.html' />"

the files are not excluded from the deployment. It doesn't seem to like the "<" or ">". The exclude portion of my deployment script looks like this:

‹fileSystem area="$srcarea^" filelist="" >
‹remoteDiff area="$srcarea^">
‹pathSpecification >
‹path name="." />
‹filters>
$exclude^
‹/filters>
‹/pathSpecification>
‹/remoteDiff>
‹/fileSystem>

Has anyone done anything like this before and been successful?

Thanks,
Chris

I haven't tried it - and I'm pretty sure it was never intended for such - but you might be able to get it to work with something like:[indent]

iwodcmd start od_script.xml -k srcarea=Y:\default\main\awards\STAGING -k target=/app/htdocs/awards -k exclude="<excludePath subPath='ex.html' /><excludePath subPath='ex2.html' />"

[/indent]Or was that what you tried that didn't work and it just didn't get presented correctly in the forums?

Other alternatives include figuring out the max number of such excludes that you're going to have to insert and create dummy values for them if not used, or to create a template for the config file and generate a new config file on the fly with the proper entries.

An example of the former would be if you had a max of 3 exclusions then you might have:[indent]

iwodcmd start od_script.xml -k srcarea=Y:\default\main\awards\STAGING -k target=/app/htdocs/awards -k exclude1="ex.html" -k exclude2="ex2.html" -k exclude3="xyzzy"

[/indent] and then your config would look like:[html]

[/html]

ISCBorisB

Hello -

I'm building an workflow external task that reads in a configuration file and then calls an opendeploy script based on parameters retrieved from the file. The idea is to have the script pass along the following three things:

1. Source area
2. Target area
3. Excludes

I am struggling with the excludes as there can be more than one in the configuration file. When I pass along something like this:

iwodcmd start od_script.xml -k srcarea=Y:\default\main\awards\STAGING -k target=/app/htdocs/awards -k exclude="‹excludePath subPath='ex.html' />‹excludePath subPath='ex2.html' />"

the files are not excluded from the deployment. It doesn't seem to like the "<" or ">". The exclude portion of my deployment script looks like this:

‹fileSystem area="$srcarea^" filelist="" >
‹remoteDiff area="$srcarea^">
‹pathSpecification >
‹path name="." />
‹filters>
$exclude^
‹/filters>
‹/pathSpecification>
‹/remoteDiff>
‹/fileSystem>

Has anyone done anything like this before and been successful?

Thanks,
Chris

In addition to what has been already suggested you may perhaps try single <excludePattern> Tag and pass just the Pattern
through -k, not the whole <excludePath>Tag(s). For your sample that translates to something like

<excludePattern regex="$pattern^"/>

with the call -k "pattern=ex2?\.html$"

Migrateduser

I am struggling with the excludes as there can be more than one in the configuration file. When I pass along something like this:

iwodcmd start od_script.xml -k srcarea=Y:\default\main\awards\STAGING -k target=/app/htdocs/awards -k exclude="‹excludePath subPath='ex.html' />‹excludePath subPath='ex2.html' />"

the files are not excluded from the deployment. It doesn't seem to like the "<" or ">". The exclude portion of my deployment script looks like this:

‹fileSystem area="$srcarea^" filelist="" >
‹remoteDiff area="$srcarea^">
‹pathSpecification >
‹path name="." />
‹filters>
$exclude^
‹/filters>
‹/pathSpecification>
‹/remoteDiff>
‹/fileSystem>

Have you tried looking at the logs to see what the deployment script was expanded into, or what arguments it "saw" being passed to it? It is probably just a matter of quoting the < and > appropriately so that they get passed all the way through to OpenDeploy and don't get messed up on the command line. If iwodcmd will always be running on a Unix/Linux box then you can try reversing the quotes you use around the excludePath elements so that you have:

-k exclude='‹excludePath subPath="ex.html" /> ‹excludePath subPath="ex2.html" />'

to be more "universal", maybe the following will work:

-k exclude="\‹excludePath subPath='ex.html' /\> \‹excludePath subPath='ex2.html' /\>"

I hope it helps...
Mike