Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to publish artifacts belonging to multiple commit ids #632

Closed
klakshmikantha opened this issue Aug 14, 2024 · 2 comments
Closed

Comments

@klakshmikantha
Copy link

Release version

5.0.0

Question Details

Hi,
Currently with publisher exe, there is an option to specify a single commitid or publish everything. Is there an option to pass a collection of commitid(s) so the exe can pick all files from the commitid(s) and push them to APIM?
The reason is if some custom validations fail with an initial commitid prior to publishing, the changes for these validations will be corrected in subsequent delta commitid(s) and we need the ability to pass all such related commitid(s) in a single request with latest version of files from these commits.
Appreciate your help.

Expected behavior

Ability to specify a collection of commitid(s) when publishing to APIM so it picks latest version of files from all the specified commitid(s).

Actual behavior

A single commitid can only be passed as input to publisher exe.

Reproduction Steps

Run the publisher pipeline with commitid as input.

Copy link

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

@guythetechie
Copy link
Contributor

We don't support that, unfortunately. You will have to loop through commit IDs and pass them one at a time to the publisher. See the discussion in #154.

@guythetechie guythetechie closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants