Render repository configuration #317
Assignees
Labels
Comments
|
Issue is stale, CC: @g4s8 |
|
@olenagerasimova @genryxy please update the page for repositories you are working on |
g4s8
pushed a commit
to artipie/management-api
that referenced
this issue
Aug 11, 2021
Added description for several repositories. Issue: artipie/artipie#317 PR: #44
g4s8
pushed a commit
to artipie/management-api
that referenced
this issue
Sep 8, 2021
Added anaconda repository option to dashboard and configuration description. Ticket: artipie/artipie#317
g4s8
added a commit
to artipie/management-api
that referenced
this issue
Dec 22, 2021
* Add absent repos * cicd(release): added release config for #38 * Fixed parameters and storage settings format in `ApiRepoUpdateSlice` Closes #39 - fixed 2 problems in ApiRepoUpdateSlice: 1) parameters separator was expected to be ; instead of & 2) storage settings were always expected to be yaml, but there also can be string for default value PR: #40 * Repo config should be url decoded Closes #39 - Body with repo configs should be url-decoded. PR: #41 * Improved updating storage settings functionality (#43) Closes #42 - simplified and fixed updating storage scenario in ApiRepoUpdateSlice. On dashboard we always work with whole yaml repo settings, so there is no need to update section by section, we can simply rewrite the whole file after checking that required fields (type and storage) are present in the new version. * fix: added repository configuration descriptions Added description for several repositories. Issue: artipie/artipie#317 PR: #44 * fix: handle errors in `ApiRepoUpdateSlice` (#45) Handle errors in `ApiRepoUpdateSlice` (#45) Closes: artipie/artipie#320 * feat(conda): added conda repository to dashboard (#46) Added anaconda repository option to dashboard and configuration description. Ticket: artipie/artipie#317 * doc: verbose link name Clarified API reference link name. Closes: #47 * fix: add rq line to get users in `FromRqLine` (#48) Part of artipie/artipie#965 Added rq line to get users in FromRqLine, corresponding test and updated http and asto. * feat: added slice for repo delete (#49) Add slice to delete a repo. Added disabled test for this slice as it is necessary to implement delete operation in FakeConfigFile class. Ticket: artipie/artipie#321 * feat: add slice for routing `POST` requests (#51) Added slice ApiRepoPostRtSlice for routing post requests by parsing body content. This class will be used in artipie module. Test will be added in next PR. Ticket: artipie/artipie#321 * deps: bumped ppom and other deps (#53) * Bumped ppom from 0.5.1 to 1.1.0 * Bumped asto from v1.9.0 to v1.10.0 * Bumped http-client from 0.3.2 to 0.3.6 * Bumped vert-server from 0.4 to 0.5 * refactor: extract class for body parsing (#52) Extract class for parsing body content for receiving some content. Close: #50 * test: enable test for delete and add for postRt (#55) Enable and a bit extend test for ApiRepoDeleteSlice and add test for ApiRepoPostRtSlice. Ref: artipie/artipie#321 * refactor: use storages instead of settings storage Co-authored-by: Kirill <g4s8.public@gmail.com> Co-authored-by: Alena <olena.gerasimova@gmail.com>
g4s8
added a commit
to artipie/management-api
that referenced
this issue
Dec 27, 2021
* Add absent repos * cicd(release): added release config for #38 * Fixed parameters and storage settings format in `ApiRepoUpdateSlice` Closes #39 - fixed 2 problems in ApiRepoUpdateSlice: 1) parameters separator was expected to be ; instead of & 2) storage settings were always expected to be yaml, but there also can be string for default value PR: #40 * Repo config should be url decoded Closes #39 - Body with repo configs should be url-decoded. PR: #41 * Improved updating storage settings functionality (#43) Closes #42 - simplified and fixed updating storage scenario in ApiRepoUpdateSlice. On dashboard we always work with whole yaml repo settings, so there is no need to update section by section, we can simply rewrite the whole file after checking that required fields (type and storage) are present in the new version. * fix: added repository configuration descriptions Added description for several repositories. Issue: artipie/artipie#317 PR: #44 * fix: handle errors in `ApiRepoUpdateSlice` (#45) Handle errors in `ApiRepoUpdateSlice` (#45) Closes: artipie/artipie#320 * feat(conda): added conda repository to dashboard (#46) Added anaconda repository option to dashboard and configuration description. Ticket: artipie/artipie#317 * doc: verbose link name Clarified API reference link name. Closes: #47 * fix: add rq line to get users in `FromRqLine` (#48) Part of artipie/artipie#965 Added rq line to get users in FromRqLine, corresponding test and updated http and asto. * feat: added slice for repo delete (#49) Add slice to delete a repo. Added disabled test for this slice as it is necessary to implement delete operation in FakeConfigFile class. Ticket: artipie/artipie#321 * feat: add slice for routing `POST` requests (#51) Added slice ApiRepoPostRtSlice for routing post requests by parsing body content. This class will be used in artipie module. Test will be added in next PR. Ticket: artipie/artipie#321 * deps: bumped ppom and other deps (#53) * Bumped ppom from 0.5.1 to 1.1.0 * Bumped asto from v1.9.0 to v1.10.0 * Bumped http-client from 0.3.2 to 0.3.6 * Bumped vert-server from 0.4 to 0.5 * refactor: extract class for body parsing (#52) Extract class for parsing body content for receiving some content. Close: #50 * test: enable test for delete and add for postRt (#55) Enable and a bit extend test for ApiRepoDeleteSlice and add test for ApiRepoPostRtSlice. Ref: artipie/artipie#321 * fix: delete from items from substorage Co-authored-by: Kirill <g4s8.public@gmail.com> Co-authored-by: Alena <olena.gerasimova@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dashboard repository page should render repository configuration. E.g. maven repository can render settings for
pom.xmlor~/.m2/settings.xml, Docker registry instructions for pull and push, etc.The text was updated successfully, but these errors were encountered: