From a5f250a5028fbf42e88cd2e9c227c3645191e4d7 Mon Sep 17 00:00:00 2001 From: Daniel Chambers Date: Fri, 2 Feb 2024 18:23:49 +1100 Subject: [PATCH] Add build inputs vs configuration open question --- rfcs/0001-packaging.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/rfcs/0001-packaging.md b/rfcs/0001-packaging.md index cde14233..86e2b2b1 100644 --- a/rfcs/0001-packaging.md +++ b/rfcs/0001-packaging.md @@ -196,6 +196,11 @@ In this mode, connectors can provide some native way of performing a hot-reloadi For example, for the NodeJS Lambda Connector, it could set the watch shell command to `npm run watch`, which would run the connector and activate its built-in hot-reloading functionality. ## Open Questions +### Build Inputs vs Configuration +- Is there a difference between Docker build inputs and connector configuration files (currently the RFC does not distinguish these)? If so: + - Can connector configuration be optional (defaulted to zero files) where it is not used (ie NodeJS Lambda Connector) + - How is the difference represented on disk in the user's Hasura project? (Different directories?) + ### Custom CLI Plugins - Do connectors need to declare if they have a custom CLI plugin? - If custom CLI plugins provide configuration update services (such as DB schema introspection), does this need to be integrated with watch mode, and if so, how is this declared?