GoogleCloudPlatform / cloud-code-vscode

Cloud Code for Visual Studio Code: Issues, Documentation and more
Other
415 stars 111 forks source link

Apigee - Ability to import API Proxies and Shared Flows to Apigee Workspace in the extracted directory form #889

Open ronson-fsrv opened 6 months ago

ronson-fsrv commented 6 months ago

Use case Currently, in the Apigee Workspace within Google Cloud Code extension for Visual Studio Code, users are provided with options to either create a new API Proxy or Shared Flow within the workspace or import a bundle in zip format. image

However, in our organization, we utilize a proxy generation engine that creates the proxies and uploads them to our Source Code Management (SCM) platform, specifically GitLab. Upon pulling the repository from GitLab, our workflow requires us to import the pulled directory of an API Proxy or Shared Flow into the Apigee Workspace. Presently, this process necessitates manual editing of the Apigee Workspace JSON file to include the repository in the workspace. image

Feature We propose adding the functionality to browse and import extracted folder versions of API Proxy and Shared Flow bundles. Currently, only .zip files can be imported into the Workspace. By allowing the direct import of folders, users would have greater flexibility. However, to ensure proper import, the system should validate that the selected folder contains the required apiproxy/sharedflowbundle directory. If this directory is not found, the import process should be rejected with an error message. The extracted folder version that we have, maintains the expected structure required by Apigee. image Please let us know if any additional information is needed.