alefcarlos / plusultra-dotnet-backstage-plugins

Backstage plugins collections for dotnet

Backstage

This is your newly scaffolded Backstage App, Good Luck!

To start the app, run:

yarn install
yarn dev

plusultra-dotnet-backstage-plugins's Issues

dotnet:new brakes after adding "targetPath"

I was testing this plugin and it works fine until I have specified "targetPath: littlepath" in the dotnet:new action.

Worth to mentione that "littlepath" folder do not exist :)

And here is the output...

12022-10-04T11:48:55.000Z Beginning step Dotnet new webapi
22022-10-04T11:48:56.000Z info: Running dotnet new webapi script with dotnet:new scaffolder action, workspace path: /tmp/16885689-e1fc-4d3a-8513-81435cf1b9ee/littlepath {"timestamp":"2022-10-04T11:48:56.009Z"}
32022-10-04T11:48:56.000Z Error: spawn dotnet ENOENT
4 at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
5 at onErrorNT (node:internal/child_process:478:16)
6 at processTicksAndRejections (node:internal/process/task_queues:83:21)

action | dotnet:template:install

We are getting the following error on our Backstage instance:

[1] 2023-07-06T14:02:03.940Z Beginning step Install template
[2] 2023-07-06T14:02:03.977Z Error: spawn dotnet ENOENT
[3]     at ChildProcess._handle.onexit (node:internal/child_process:283:19)
[4]     at onErrorNT (node:internal/child_process:476:16)
[5]     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Our Template structure:

    [...]

    - id: install_template
      name: "Install template"
      action: dotnet:template:install
      input:
        package: ./dotnet-api-example-template
        args:
          - --force

    - id: create_template
      name: "Create template"
      action: dotnet:new
      input:
        template: apiexample
        args:
          - -n
          - ${{ parameters.projectName }}
   
    [...]

Follow-up: @jpcarpanezi

runCommand is deprecated

The deprecated runCommand was removed in Backstage Scaffolder Backend 0.18.0 in favour of executeShellCommand. This makes the plugin not compatible with recent versions of Backstage.

dotnet:new brakes after adding targetPath"

12022-10-04T11:48:55.000Z Beginning step Dotnet new webapi
22022-10-04T11:48:56.000Z info: Running dotnet new webapi script with dotnet:new scaffolder action, workspace path: /tmp/16885689-e1fc-4d3a-8513-81435cf1b9ee/littlepath {"timestamp":"2022-10-04T11:48:56.009Z"}
32022-10-04T11:48:56.000Z Error: spawn dotnet ENOENT
4 at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
5 at onErrorNT (node:internal/child_process:478:16)
6 at processTicksAndRejections (node:internal/process/task_queues:83:21)

action: dotnet:template:install doesn't support Installation of templates from folder

Hey,

I have tried to install dotnet template from the folder and it says NO :/

- id: donettemplateinstall
      name: Dotnet template install
      action: dotnet:template:install
      input:
        package: ./dotnet/little-template
        args: []

Error that I am getting:

Command dotnet failed, exit code: 9
12022-10-05T15:38:03.000Z Beginning step Dotnet template install
22022-10-05T15:38:03.000Z The following template packages will be installed:
32022-10-05T15:38:03.000Z ./dotnet/little-template
42022-10-05T15:38:03.000Z ./dotnet/little-template is not supported.
52022-10-05T15:38:03.000Z Error: Command dotnet failed, exit code: 9
6    at ChildProcess.<anonymous> (/home/tms/repos/backstage-app/app/node_modules/@backstage/plugin-scaffolder-backend/dist/index.cjs.js:869:11)
7    at ChildProcess.emit (node:events:513:28)
8    at ChildProcess.emit (node:domain:489:12)
9    at maybeClose (node:internal/child_process:1093:16)
10    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

I know for sure that template is valid and working just fine. Also folder "dotnet" exist in the main folder with a list of templates.

What I would like to have:

1. Ability to install dotnet templates from the folder on the disk (which was fetched from another repo for example)
2. Install multiple templates by pointing to the main folder which contains of several templates.
3. Check if template already exist - otherwise it would fail if you try to add same template...

Thanks ;)