Please consider supporting create, update, and delete operations on forms, via the [ProForma Forms API|https://confluence.atlassian.com/proformadev/proforma-developer-documentation-1167691695.html.
These operations being API-initiated would allow JSM to serve as a front-end atop GitOps workflows, with the following benefits:
- Facilitate users working in their preferred tool.
- Support continued relevance for JSM, hedging against further enhancment to the GitOps user experience on VCS platforms.
- Qualify JSM for use in increasingly heterogeneous environments.
Create and update operations might be implemented with the Forms API accepting in its request payload
- Field metadata (e.g. a [JSON Schema|https://json-schema.org/]), or raw HTML, optionally linked as a URL
- a dry-run mode (validate, render, but don't publish)
- a strict mode flag
- an optional form template ID
- an optional style/theme
- an optional rendering engine
Accompanying endpoints to list form templates, styles/themes, and rendering engines might be needed too.
Some kind of pairing protocol might be needed too, i.e. to associate a JSM portal and request type with a Git repository and branch or path.
I'd be happy to explore this further with you.
Thanks,
Val
- links to
