This is a Bug Report

Description

Currently it is possible to execute a Serverless command while another one is still running (e.g. package is running and you invoke deploy). This leads to a messed up serverless run, because Serverless is designed to run only one command at a time.

The extension should store a flag in the extension context that indicates if a command is currently active. Any further command execution should show an error, as long as the current command has not been finished.

Additional Data

• Extension version: 0.0.4
• Serverless Framework:
  Version: any

• Serverless installed globally

• Operating System: any
• Stack Trace (if available):

This is a Question

Description

The extension should be universal. To be proven as that, we should try to get feedback on how it behaves for other providers.
There might be the need to have some adaptions in the configuration, etc. depending on the selected provider.

If you see this task, use VSCode but anything else than AWS, please provide feedback.

This is a Feature Proposal

Description

The extension should allow invoking serverless deploy. The command shall be contained in the top hives' context menus.

The current version only supports locally installed per project serverless instances.
It should support global serverless installations too.

This is a Bug Report

Description

• What went wrong?
  The Package service and Deploy service commands are shown in all context menus. This can be seen when you right-click any file node in the VSCode explorer tree.

• What did you expect should have happened?
  They should only appear in the Serverless outline.

• What stacktrace or error message from your provider did you see?
  N/A

Additional Data

• Extension version: 1.0.0
• Serverless Framework: N/A
  Version:

• Serverless installed globally

• Operating System:
• Stack Trace (if available):

The following topics should be resolved

• TSLint
• AppVeyor
  Travis Not important right now as AppVeyor already tests everything
• Unit tests
• Coverage / Coveralls

New issues and PRs should load a GitHub template to unify the reports.
This makes processing and planning much easier

This is a Feature Proposal

Description

Instead of only asking for the stage when running commands, the extension should also be able to ask for a region.
As the default region most likely covers most service setups, the availability of the region text input box can be added as configurable feature. The extension configuration should contain a boolean flag (askForRegion) that can be used to enable or disable the text input per workspace or globally.

This is a Bug Report / Question

Description

Trying to build the extension in order to test/submit a PR.

• What went wrong?

Cannot build master branch

• What did you expect should have happened?

Source should have built

• What was the config you used?

node@8 and node@11, usual npm install, building inside VSC

• What stacktrace or error message from your provider did you see?

Build exits with this error:

src/lib/serverlessOutline.ts(124,31): error TS2459:
   Type 'string' has no property 'http' and no string index signature.

Is there a configuration etc. that I'm missing?

This is a (Feature Proposal)

Description

For bug reports:

• What went wrong?
• What did you expect should have happened?
• What was the config you used?
• What stacktrace or error message from your provider did you see?

For feature proposals:

• User creates a Serverless service, containing n functions. User deploys the service, AWS allocates a randonly named API gateway URL for the service, suffixed with each function. User wants to open one or more functions in a browser.
• Might be sensible to enable 'open all functions in browser' or 'open this function in browser' by default?

Similar or dependent issue(s):

• none

Additional Data

• Extension version:
• Serverless Framework:
  Version:

• Serverless installed globally

• Operating System:
• Stack Trace (if available):

This is a Feature Proposal

Description

The plugin should set the defaultRegion parameter to an empty string, so that it would not add any region parameter to the serverless command line. This will automatically use the user's configured project region (serverless.yml) in the first place. Otherwise it could lead to an unexpected deployment into the wrong region (thanks @panzupa).

Similar or dependent issue(s):

• #1 (comment)

Additional Data

• Extension version:
• Serverless Framework:
  Version:

• Serverless installed globally

• Operating System:
• Stack Trace (if available):

The API hive is currently empty.
It should display the whole service API structure (combination of all function endpoints, shown like the deployed API Gateway)