1/15/2024 0 Comments Splunk phantom integrationThe metadata YAML will contain the details provided by the user, and theĬonnector module will define an example connector implementation. $ phantom-dev create "My Special App"Ī new project directory will be created and populated with a metadata.yaml Running phantom-dev create will prompt the user for the set of details Implement this behaviour or forgo the use of debug.Īside from these limitations, phantom-dev should work normally withĪny Phantom app once extracted into a project directory. While phantom-dev apps implement this by default, other apps will have to json metadata file.Ĭertain packaging features, such as autopopulation of dependency metadata,įinally, the debug command will not work unless the app is configured as aĭebugpy listener when executed as _main_. json file is used instead of metadata.yaml, phantom-dev will Metadata from code implementations, metadata inference will not work withĪ connector that has been implemented without phantom-dev.įull specification of app metadata must therefore be provided in either Compatibility with Apps Not Created with phantom-devīecause phantom-dev relies on specific library features to infer action If the current commit doesn't have a version label, roboversion will createĪ unique development version using the most recent version tag. To set the version, tag the current commit with a version label Unless a version is explicitly specified in the app metadata,Īutomatically detect the project version from git repository state. With as normal, in accordance with the official Phantom documentation. Make full use of the module without being concerned with managing it as aĮdge cases and use of more specialised BaseConnector methods should be dealt The phantom_dev.action_handler module will be automatically embedded in theĭependencies directory when the app is built, allowing the developer to The implementation assuming parameters are type-annotated in the code. Phantom_dev.action_handler.ActionHandler decorator will be used toĭynamically infer action metadata unless overridden in the metadata file.Īction names, parameter names, and parameter types can all be inferred from Of a phantom.base_connector.BaseConnector subclass, which is the basis for The phantom_dev.action_handler module greatly simplifies the implementation ![]() Than a list of action objects with unique and potentially conflicting names).įor information on the generated app metadata, see the official Phantom JSON actions is now a mapping of action names to action data, rather JSON project-* keys are defined under the project object in the YAML)Īnd lists of uniquely-identifiable objects have been converted to objects Related keys have been grouped under a common prefix key Minor alterations to the JSON structure have been made to assist with The metadata.yaml file in the project directory will be used to generate theĪpp JSON expected by the Phantom platform. Phantom-dev is a command-line utility for creating, building, and deployingĪpp packages are built from project directories containing a YAML metadata fileĪny other files in the project directory will be packaged and included with ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |