wso2 / wso2/docs-apim

The Example Block in Externalizing the VCS Configuration Section Should be Corrected

Open
#6,473 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
99
Forks
708
Avg merge
1d 7h
Merged PRs (30d)
22

Description

Description:

  • The example block in [1] which provides an example code segment for setting a custom location for the vcs-config.yaml file specifies only the folder location as follows.
$ apictl set --vcs-config-path /home/wso2/api-manager/gitconfigs
VCS config file path is set to : /home/wso2/api-manager/gitconfigs
  • This causes an issue as reported in [2]. This code segment should be corrected to include the vcs-config.yaml file name as well as shown below.
$ apictl set --vcs-config-path /home/wso2/api-manager/gitconfigs/vcs-config.yaml
VCS config file path is set to : /home/wso2/api-manager/gitconfigs/vcs-config.yaml
  • An example of how this command should be run with the relevant output is shown in point 6 of [3].

  • This needs to be fixed in the documentation spaces from 3.2.0 and above.

[1] https://apim.docs.wso2.com/en/latest/install-and-setup/setup/api-controller/advanced-topics/configuring-git-integration/#externalizing-the-vcs-configuration
[2] https://github.com/wso2/api-manager/issues/927
[3] https://github.com/wso2/api-manager/issues/927#issuecomment-1327121403

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the linked Externalizing the VCS Configuration documentation and compare the example with point 6 of the referenced api-manager issue. Update the example in documentation spaces for version 3.2.0 and above so the path includes vcs-config.yaml, then verify the command and displayed output are consistent.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.