You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My ideal workflow would allow me to "force update" the service configuration from within the service page itself (see picture). I haven't used your software enough to know whether there's an easy mapping from import job to service, but it'd greatly help developing and testing mocks/specs on localhost if these could be manually reimported without switching page.
Related Extra:
I would also add a last fetched timestamp rather than just last updated in the service description:
Without surfacing that information, I have a hard time feeling sure that the update job has been run as expected if my definition ends up not changing. This makes it harder to pinpoint whether the bug is on my or the importer's side without looking at the docker-compose logs.
(Let me know what you think of this, and whether this should be its own issue)
The text was updated successfully, but these errors were encountered:
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.
From #474.
My ideal workflow would allow me to "force update" the service configuration from within the service page itself (see picture). I haven't used your software enough to know whether there's an easy mapping from import job to service, but it'd greatly help developing and testing mocks/specs on localhost if these could be manually reimported without switching page.
Related Extra:
I would also add a
last fetched
timestamp rather than justlast updated
in the service description:Without surfacing that information, I have a hard time feeling sure that the update job has been run as expected if my definition ends up not changing. This makes it harder to pinpoint whether the bug is on my or the importer's side without looking at the
docker-compose
logs.(Let me know what you think of this, and whether this should be its own issue)
The text was updated successfully, but these errors were encountered: