Yes, definitely the REST API documentation needs to be updated. The incorrect documentation caused us a lot of time and trouble.
Now, as far as the functionality of the REST call (and probably the action, although I didn’t test that specifically), it is NOT possible to load just definitions.
If you do a lot of tokenization, you will end up needing a file with the token defs, and environment-specific files with the values.
You can load a file with just token values, no problem.
But if you try to load a file with just definitions, it fails unless you add “” after the close of the definitions tag. Doesn’t matter if the environment exists or not, you just need to have the values block with an environment name.
It would be VERY useful to be able to load definitions and/or values simultaneously or separately instead of having to manipulate the definitions file manually.
Am I making any sense here?
Senior Enterprise DevOps Architect