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

Use REST API or a baseline to help operator deploy all recommended periodic items in C3 #21

Open
jgstew opened this issue Sep 23, 2016 · 3 comments

Comments

@jgstew
Copy link

jgstew commented Sep 23, 2016

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.

@strawgate
Copy link
Owner

I wish we could publish baselines with bigfix.me....

Until then it's either a guide in the wiki that nobody will ever read or something with the REST API

Do people use the REST API fixlets? Is it a lot of trouble to support if they have issues?

@jgstew
Copy link
Author

jgstew commented Oct 3, 2016

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.

@jgstew
Copy link
Author

jgstew commented Apr 5, 2017

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.

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