Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Ignore warning while importing package through script mode

Avatar

Avatar
Validate 1
Level 2
kaushal13
Level 2

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
Boost 1
View profile

Avatar
Validate 1
Level 2
kaushal13
Level 2

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
Boost 1
View profile
kaushal13
Level 2

14-11-2019

Hi,

we have a requirement to ignore warning for one of the package type to import it.

Can some one help what should be added or command for doing that.

package -instance:stage -import:/sftp/incoming/from_campaign/test/<%= instance.vars.packageName %> -verbose

when importing manually it fails if you do not select ignore warning because the package has some reference to internal value not present in next environment.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Contributor
MVP
wodnicki
MVP

Likes

923 likes

Total Posts

1,050 posts

Correct Reply

492 solutions
Top badges earned
Contributor
Shape 1
Give Back 100
Give Back 50
Give Back 25
View profile

Avatar
Contributor
MVP
wodnicki
MVP

Likes

923 likes

Total Posts

1,050 posts

Correct Reply

492 solutions
Top badges earned
Contributor
Shape 1
Give Back 100
Give Back 50
Give Back 25
View profile
wodnicki
MVP

18-11-2019

Hi,

In the <package/> node at the top of your xml add ignoreWarnings="true"; maybe something like `perl -pi -e 's/<package/<package ignoreWarnings="true"/' file` ahead of the import call.

Obligatory note of caution:

It looks like you're automating import of campaigns uploaded to an sftp. Just know that there is a ton of danger in this, ranging from innocuous user error to not-so-innocuous trivial root exploitation of the app. If you're sure of this approach, consider at least adding a check to constrain import to nms:operation schema.

Thanks,

-Jon

Answers (1)

Answers (1)

Avatar

Avatar
Level 1
aneeshu1768888
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
aneeshu1768888
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

0 solutions
View profile
aneeshu1768888
Level 1

21-04-2020

Hi : I tried with ignoreWarning = "true" but it doesn't work. Do you know the correct format how it can be given in the below schema xml file which we import

 

<package author="test" buildDate="2019-07-09 08:36:27.500Z"
buildNumber="8850" buildVersion="6.7" img="xtk:installedPackage.png" label="Shared schema"
name="sharedSchemas" namespace="test" vendor="">