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

Allow different artifacts of same type for the same API version #849

Open
lbroudoux opened this issue Jun 21, 2023 · 2 comments
Open

Allow different artifacts of same type for the same API version #849

lbroudoux opened this issue Jun 21, 2023 · 2 comments

Comments

@lbroudoux
Copy link
Member

Reason/Context

Since we enabled Multi-artifacts support in Microcks, we discovered many new use cases such as the one of adding different Postman Collections that hold tests suites of different levels or tests suites for different consumers (eg. consumer-driven contract testing).

For testing / performance / traceability concerns, we recently add the support of storing Postman Collection in the database (see #255) and are on our way to doing the same things for SopaUI (see #826). However, when saved, artifacts are just named using the API version and name (ex: API Pastris-1.0.0.json).

Description

This undoubtedly will lead to collision and erasure of information. We need to fix this in order to avoid losing information.

Implementation ideas

No response

@lbroudoux
Copy link
Member Author

We need further discussion to make up our minds on this one. Ideas more than welcome!

@lbroudoux lbroudoux modified the milestones: 1.8.1, 1.9.0 Jan 4, 2024
Copy link

github-actions bot commented Feb 4, 2024

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale State due to inactivity label Feb 4, 2024
@lbroudoux lbroudoux added keep-open Explicitily keep open and removed stale State due to inactivity labels Feb 6, 2024
@lbroudoux lbroudoux modified the milestones: 1.9.0, 1.9.1 Mar 7, 2024
@lbroudoux lbroudoux modified the milestones: 1.9.1, 1.10 May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant