we have a packaged a plumber API by following the proposed method from this repo resulting from this discussion in the community forum.
The package structure is needed to be able to properly test the API's function. However, it does complicate deployment to RSConnect quite a bit with a CI/CD workflow.
For production usage, we depend on being able to properly test a package before releasing it.
Since the plumber API is a package now, RSConnect is not able to find the package's functions. It would also be possible to publish the package to our RSPM, but then we would have to adapt the manifest each and every time we want to release a new version to RSConnect. Also, a two-fold approach would be needed (which is not ideal):
- publish package to RSPM
- publish plumber API with package to RSConnect after updating manifest
Is there an easier solution to the problem?
Thanks in advance !