I just realized that ephemeral tagging was never implemented.

This leads to a bit of an issue since ephemerals have some weirdness with leading/trailing slashes that need to be worked out better.

Ephemerals uses "/"+params[:splat][0] so we're going to go with that for now.

Need to add support for an audit trail

Using the same method as tagging, we need to DRY up the links and watches code as well.

Not sure how many to keep at this point. Consider implementing some form of limited versioning.

The idea is to allow callback data to be custom formatted by the plugin. Essentially the plugin writer would provide a method that could be called if it exists to format the response in a custom way.

Use case: RunDeck
RunDeck requires data to be in a certain format. See here under File Formats. The idea is that, in lieu of using Ephemerals to store the XML, we would be able to push updated resource data to RunDeck so it can consume it (say, new entries to the Host primitives)

Right now, the configurations top-level path accepts an optional query param short=true. This provides a condensed view of all configurations. In the interest of consistency, that same option should be allowed, at minimum, on the other primitive top-levels.

This might lead into other "filters" as query params which means the whole process of filtering needs to be handled better. For now, I'm only interested in the condensed view.

Request came in on IRC to see about adding filtering on paths for status:

/services/http/down
or /services/status/down (for all)

Same for hosts.

One issue that has come up from internal usage at VA is that listing large numbers of configurations (even with existing levels of specificity) is a bit cumbersome.

We're currently storing 180+ json configuration settings under a single tag. Some of these configurations are 32k in size. Pulling back all of these is rather cumbersome to enumerate client side.

Need a method for possible getting back a truncated view of items (possibly ?truncated=true or /*/truncated) that doesn't actually return the contents of the configuration but just the names and timestamp parameters. Possible providing a link to the full configuration (though that seems redundant.)

So I thought it would be nice and easy if folks could just append an action to the end of a URL (i.e. /tag, /link, /watch). This worked great when the 4 original primitives were in there. Ephemerals went and screwed that up.

As it stands, the current API for doing those operations will mean that Ephemeral paths cannot end in /tag,/link,/watch until that changes (if it does). I'm somewhat okay with this for now. You can still have it in the rest of the URL for an ephemeral, just not at the end.

This is a place holder to remind me how shortsighted I was.

Per @joemiller on irc:

"was hoping for a super lazy "POPULATE!" button =)"

via @tobert (here and on IRC)

Some way to hit a node via curl/wget that provides a long-poling interface to watch for changes

Possible paths:

http://noahserver/watch/node_type/node_name

Need to add the url to the object in the body of the watch message when it is fired. This is similar to pub category but should provide the URL of the CRUDed object to be more informative.

The current "mimetype" implementation is ghetto. This should be changed to use the Accepts header to specify content type for both read and write.

Decide on and implement some form of authentication. Most likely token based similar to how links/tags work. I.E.

GET /applications/some_app/token - Generates a new token for usage
DELETE /applications/some_app/token - Pass token id as JSON body
PUT /applications/some_app/token - Allow a user generated token for access control

Because of the currently terrible coupling of the watcher daemon to the Ruby API, changing the connection host doesn't work. The libraries being pulled in use REDIS_URL but the binscript does not.

As an interim to the breakout of agent into its own gem, need to build in CLI options to set that properly so it will work.

This became visible when using the noah cookbook to install which puts redis on port 6381.

The flow:

Crete two ephemerals "/mydata/eph1" and "/mydata/eph2":
PUT http://my_host:5678/ephemerals/mydata/eph1
data1
PUT http://my_host:5678/ephemerals/mydata/eph2
data2

relate it to tag "mytag":
PUT http://my_host:5678/ephemerals/mydata/eph1/tag
{"tags":"mytag"}
PUT http://my_host:5678/ephemerals/mydata/eph2/tag
{"tags":"mytag"}

Currently I can get all ephemerals by tag by:
GET http://my_host:5678/tags/mytag

Delete one of ephemerals by
DELETE http://my_host:5678/ephemerals/mydata/eph1

Now, when I try to get it by tag again I got error:
{"result":"failure","error_message":"undefined method `name' for nil:NilClass"}