Skip to content
This repository was archived by the owner on Apr 13, 2020. It is now read-only.

Conversation

@samiyaakhtar
Copy link
Collaborator

@samiyaakhtar samiyaakhtar commented Apr 7, 2020

This is part 1 of microsoft/bedrock#1173. The second part will be running this command as part of pipelines to get the right service name, but that will be merged after an spk release is available with the changes in this PR.

Screen Shot 2020-04-07 at 7 06 50 PM

Related to microsoft/bedrock#1173

evanlouie and others added 11 commits April 2, 2020 04:30
- Updated bedrock.yaml `services` to contain a list of services instead of a map
  indexed by path.
  - Auto-migration of bedrock.yaml is hooked into `read()` function of the
    `bedrockYaml.ts` file.
    - `read()` is now the only function used for loading the bedrock.yaml file;
      `Bedrock()` in `config.ts` is now noted as deprecated and now calls
      `read()` under the hood.
  - `path` property for a service now tracks the path to the service.
  - Documentation references all updated.
- `spk service create <service-name>` now follows the spec
  `spk service create <service-name> <service-path>`
  - Documentation references all updated.
  - Integration tests updated.
- Updated bedrock.yaml `services` to contain a list of services instead of a map
  indexed by path.
  - Auto-migration of bedrock.yaml is hooked into `read()` function of the
    `bedrockYaml.ts` file.
    - `read()` is now the only function used for loading the bedrock.yaml file;
      `Bedrock()` in `config.ts` is now noted as deprecated and now calls
      `read()` under the hood.
  - `path` property for a service now tracks the path to the service.
  - Documentation references all updated.
- `spk service create <service-name>` now follows the spec
  `spk service create <service-name> <service-path>`
  - Documentation references all updated.
  - Integration tests updated.
Copy link
Collaborator

@mtarng mtarng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm. Overall I think this logic should probably fall under spk service commands, and there should be a parameter for the service "index" or path.

Is this command designed to run in the service build pipeline, and so the design assumes you're in the service directory?

@samiyaakhtar samiyaakhtar requested a review from dennisseah April 7, 2020 16:39
@samiyaakhtar samiyaakhtar changed the title Adding spk project get-display-name command Adding spk service get-display-name command Apr 7, 2020
Copy link
Collaborator

@dennisseah dennisseah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where is get-display-name.md?
please write more tests, like

  1. opts.path is incorrect.
  2. yaml file does not have the service name.
    please do not stop are only these two tests

thanks

@samiyaakhtar samiyaakhtar merged commit 543e518 into CatalystCode:master Apr 9, 2020
@samiyaakhtar samiyaakhtar deleted the 1173_1 branch April 9, 2020 01:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants