List of field names to avoid for Option Inputs

Provisioning & Self Service
, , , , ,
1

Hello,

I’ve compiled a list of field names to avoid for Option Inputs if possible.

Here are some fieldNames to avoid that are used in generating the policy config while provisioning an instance:

copies
scaleFactor
image
loadBalancerConfig
virtualImageId
template
servicePlanOptions
containerCount
loadBalancerCount

Here are the fieldNames to avoid that are used in the Morpheus API option lists:

zoneId
cloudId
zone
server
network
router
storageServer
domain
parent
siteId
site
instance
groupId
group
config
instanceType
loadBalancerId
layout
provisionType

Using these reserved fieldNames could lead to deployment issues. Below are some example errors.

Using Field Name “network” for an input:

2024-04-29_14:34:45.76111 ''[2024-04-29 14:35:00,836] [http-nio-127.0.0.1-8080-exec-12] [1;31mERROR[0;39m [36mStackTrace[0;39m - Full Stack Trace:
2024-04-29_14:35:00.83679 'groovy.lang.MissingPropertyException: No such property: zone for class: java.lang.String

Using another reserved Field Name “image” for an input:

2024-06-06_11:56:50.58481 ''[2024-06-06 11:56:50,680] [appJobHigh-3] ERROR c.m.i.ScribeService - error provisioning order instance: groovy.lang.MissingPropertyException: No such property: platform for class: java.lang.String
2024-06-06_11:56:50.68092 'groovy.lang.MissingPropertyException: No such property: platform for class: java.lang.String

We have plans to add a warning on the form to warn the users to avoid using any of the above.

Thanks!

2 Likes