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
There are many fixlets / tasks in C3 that should be run on a periodic basis on the systems that are relevant to them, while others would require a more careful choice by the operator.
It would be nice to have a REST API script/fixlet or a baseline or both to help the operator deploy all recommended periodic items.
It would also be useful to have a list of them all somewhere.
This is not just about C3 Inventory, but applies to many of the C3 content repos.
The other issue is what happens when one of these periodic items are updated? I guess it makes sense to stop a baseline/multi-action and restart it from the new version.
The text was updated successfully, but these errors were encountered:
I don't know how often anyone actually uses REST API Fixlets, though I do have them working on both Windows and Linux now because of my use of cURL. They don't currently work on Mac because of XML inspector dependencies.
If you aren't actually creating content with them, only deploying existing content, then it could be much simpler.
I think a dashboard that uses the REST API or other methods to deploy the periodic items would be better than a REST API fixlet. I definitely don't think the REST API fixlet is the best choice anymore.
There are many fixlets / tasks in C3 that should be run on a periodic basis on the systems that are relevant to them, while others would require a more careful choice by the operator.
It would be nice to have a REST API script/fixlet or a baseline or both to help the operator deploy all recommended periodic items.
It would also be useful to have a list of them all somewhere.
This is not just about C3 Inventory, but applies to many of the C3 content repos.
The other issue is what happens when one of these periodic items are updated? I guess it makes sense to stop a baseline/multi-action and restart it from the new version.
The text was updated successfully, but these errors were encountered: