File upload or reference as part of plugin install

[jmthomas]

When installing a plugin sometimes you need additional files. For example when installing FPrime you need a json file to configure it. During the COSMOS plugin installation, the user should be prompted to provide a file which is then uploaded to the correct place and used via the plugin.

You might also reference an existing file as a bucket URL (TGT/data/file.json) to use rather than upload the file. Should this open a bucket file browser? Should we support external URLs?

[jmthomas]

After implementing this, go back to the FPrime plugin and implement this feature there. Note: there are additional processes that need to run on the json file to allow FPrime to work.

[crawlchat]

This is a great feature request! Here's a summary of the current state and some thoughts to help the COSMOS engineering team scope this out:

---

📦 Current Plugin Variable System

Currently, the plugin.txt supports VARIABLE declarations that prompt the user for input during installation. These render as text fields (or dropdowns via VARIABLE_STATE) in the installation dialog.

For example:

VARIABLE fprime_config_file path/to/config.json
VARIABLE_DESCRIPTION "Path to the FPrime configuration JSON file"

This works fine for simple string paths, but there's no native support for a dedicated file-upload input type or a bucket file browser.

---

🗂️ Questions to Help Scope This Feature

To help the engineering team fully understand the requirements, a few clarifying questions:

1. New VARIABLE type? — Are you envisioning a new keyword like VARIABLE_TYPE file that would signal the UI to render a file picker instead of a text input? Or a brand-new top-level keyword like FILE_VARIABLE?

2. Upload destination — When a file is uploaded, where should it land? (e.g., TARGET/data/ in the bucket?) Should the plugin author be able to specify the destination path?

3. Bucket file browser — For the "reference an existing bucket file" use case (e.g., TGT/data/file.json), opening a bucket file browser makes a lot of sense for usability. Is this scoped to the same operator scope/environment, or cross-scope?

4. External URLs — Supporting external URLs adds complexity (auth, availability, security). Is this a hard requirement for FPrime or a nice-to-have?

---

💡 Suggested Approach (for discussion)

A possible implementation path:

• Add a VARIABLE_TYPE keyword (alongside existing VARIABLE_DESCRIPTION / VARIABLE_STATE) with a file type option
• During install, the UI renders the variable as a file picker with two modes:
  • 📁 Upload a local file → uploaded to a defined bucket path
  • 🗄️ Browse bucket → opens a bucket file browser to select an existing file
• The resolved value (bucket URL) is passed into the plugin as the variable value, usable via ERB like any other variable

External URL support could be a follow-on given the added complexity.

---

Could you confirm the intended plugin.txt syntax you have in mind, and whether the FPrime use case is the primary driver? That would help nail down the scope. 🙏