PI95915: ONLY UI ENFORCEMENT OF ALLOWED TAGS ON APPLICATION PROCESSES WITH FOR EACH TAG STEPS

APAR status

• Closed as unreproducible.

Error description

• The for each tag step allows the user to specify a set of
  resource tags. At runtime you can either use all of the tags
  originally specified or you can specify a subset of them. The
  for each tag step should only execute on resources with the tags
  that you indicated. However, the enforcement of which tags can
  be specified for 'for each tag' steps is implemented through the
  UI only; the server does not enforce it. This means that if you
  are requesting the application process from udclient that you
  can pass tags to the server that are not in the original set of
  resource tags and it will run processes on resources with those
  invalid tags.
  
  Currently there is no easy way of doing this through the
  udclient. However, it is possible you have a little bit of
  knowledge about the processes that they're going to be running.
  Example JSON of running an application process that has a For
  Each Tag step.
  {
    "application": "simple-application",
    "applicationProcess": "simple-process-2",
    "environment": "simple-environment",
    "properties": {
      "ForEachTagStepName/activity.tag.ids": "SomeTagId"
    }
  }
  
  ForEachTagStepName is the name of the step in the application
  process. This name is entered by the user when dragging and
  dropping the activity into the UI. The value is a comma
  separated list of resource tag ids, a single tag id can be
  supplied. Resource tags and their ids can be found using the
  following REST endpoint:
  https://localhost:8443/rest/tag/?filterFields=objectType&filterT
  ype_objectType=eq&filterValue_objectType=Resource&name=*
  
  
  Steps to reproduce:
  1) Configure an application with an application process using a
  for each tag step and include a set of resource tags
  2) Configure resources in an environment in this application
  that have the tags from the set in step 1 but also configure
  resources with some other resource tag not specified in step 1
  3) Run the process from the UI, see that you are only given the
  option to chose from tags specified in step 1
  4) Run the process from udclient specify a tag not included in
  step one i.e. the additional tag set in step 2
  expected: the process will not run as the tag specified is not
  in the list of tags set on the activity
  actual: the process runs and executes normally.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * DevOps Deploy Web UI Users                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ONLY UI ENFORCEMENT OF ALLOWED TAGS ON APPLICATION PROCESSES *
  * WITH FOR EACH TAG STEPS                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels