Introduce 'scope' field in key value model #2669

lakshmi-kannan · 2016-05-04T21:31:12Z

TODO:

Prefix based RBAC will be in another PR. Trying to scope things down.

CLI examples:

GET

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key set company brocade     [ruby-1.9.3p484]
+------------------+---------+
| Property         | Value   |
+------------------+---------+
| name             | company |
| value            | brocade |
| expire_timestamp |         |
+------------------+---------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key get company             [ruby-1.9.3p484]
+------------------+---------+
| Property         | Value   |
+------------------+---------+
| name             | company |
| value            | brocade |
| secret           | False   |
| encrypted        | False   |
| scope            | system  |
| expire_timestamp |         |
+------------------+---------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key set boss lakstorm --scope=user
+------------------+----------+
| Property         | Value    |
+------------------+----------+
| name             | boss     |
| value            | lakstorm |
| expire_timestamp |          |
+------------------+----------+

## XXX: Get needs to be fixed so asking for something without scope "user" doesn't return it. 

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key get boss                [ruby-1.9.3p484]
+------------------+----------+
| Property         | Value    |
+------------------+----------+
| name             | boss     |
| value            | lakstorm |
| secret           | False    |
| encrypted        | False    |
| scope            | user     |
| expire_timestamp |          |
+------------------+----------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key set manas grump --scope=nsfw
ERROR: 400 Client Error: Bad Request
MESSAGE: Invalid scope "nsfw"! Allowed scopes are ['system', 'user']. for url: http://127.0.0.1:9101/v1/keys/manas

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$

LIST

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key list --scope=user       [ruby-1.9.3p484]
+------+-------+--------+-----------+------------------+
| name | value | secret | encrypted | expire_timestamp |
+------+-------+--------+-----------+------------------+
+------+-------+--------+-----------+------------------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key list --scope=system     [ruby-1.9.3p484]
+------+-------+--------+-----------+------------------+
| name | value | secret | encrypted | expire_timestamp |
+------+-------+--------+-----------+------------------+
| foo  | bar   | False  | False     |                  |
+------+-------+--------+-----------+------------------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key set boss lakstorm --scope=user
+------------------+----------+
| Property         | Value    |
+------------------+----------+
| name             | boss     |
| value            | lakstorm |
| expire_timestamp |          |
+------------------+----------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key list --scope=user       [ruby-1.9.3p484]
+------+----------+--------+-----------+------------------+
| name | value    | secret | encrypted | expire_timestamp |
+------+----------+--------+-----------+------------------+
| boss | lakstorm | False  | False     |                  |
+------+----------+--------+-----------+------------------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$

v2 API examples

PUT

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http PUT "http://localhost:9101/v2/keys/user/company" < kv.json
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive
Content-Length: 195
Content-Type: application/json; charset=UTF-8
Date: Sat, 07 May 2016 01:07:40 GMT
X-Request-Id: 24183b1b-30f1-45e3-a4ab-4460a7fa620d

{
    "encrypted": false,
    "id": "572d3fdcd9d7ed14d88a3e23",
    "name": "company",
    "scope": "user",
    "secret": false,
    "uid": "key_value_pair:user:company",
    "value": "BROcade"
}

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$

DELETE

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http DELETE "http://localhost:9101/v2/keys/user/company"
HTTP/1.1 204 No Content
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive
Content-Length: 4
Date: Sat, 07 May 2016 01:08:02 GMT
X-Request-Id: 673981e0-c1f0-4117-80cf-7d539567e64d



(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$

GET

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http "http://localhost:9101/v2/keys/user/foo"
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive


  1 {
Content-Length: 187
Content-Type: application/json; charset=UTF-8
Date: Sat, 07 May 2016 01:06:02 GMT
X-Request-Id: 1a1bfc27-c54f-4ac6-8ab9-5107954c2dd2

{
    "encrypted": false,
    "id": "572d3dd7d9d7ed0c17a9857c",
    "name": "foo",
    "scope": "user",
    "secret": false,
    "uid": "key_value_pair:user:foo",
    "value": "userbar"
}

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http "http://localhost:9101/v2/keys/system/foo"
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive
Content-Length: 187
Content-Type: application/json; charset=UTF-8
Date: Sat, 07 May 2016 01:06:07 GMT
X-Request-Id: 493f459f-b9df-4fc6-a200-d122298e61d6

{
    "encrypted": false,
    "id": "572d3dbed9d7ed0c17a9857b",
    "name": "foo",
    "scope": "system",
    "secret": false,
    "uid": "key_value_pair:system:foo",
    "value": "bar"
}

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$

v2 APIs with secrets

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http PUT "http://localhost:9101/v2/keys/user/company" < kv_secret.json
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive
Content-Length: 300
Content-Type: application/json; charset=UTF-8
Date: Sat, 07 May 2016 01:10:30 GMT
X-Request-Id: 33cc6994-f140-42a9-a3b4-31211d79220c

{
    "encrypted": true,
    "id": "572d4086d9d7ed14d88a3e24",
    "name": "company",
    "scope": "user",
    "secret": true,
    "uid": "key_value_pair:user:company",
    "value": "0083E1033A54F9FAB3336FDA3F6FE0A658A02A21DC6BA530A5FB062B13999A85418906DEE8D62CFD13BDF64863013DBEDAB998C742D4767A10"
}

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http "http://localhost:9101/v2/keys/user/company"
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive
Content-Length: 300
Content-Type: application/json; charset=UTF-8
Date: Sat, 07 May 2016 01:10:45 GMT
X-Request-Id: 45f12a60-8593-4ae1-800d-befa8590f8c0

{
    "encrypted": true,
    "id": "572d4086d9d7ed14d88a3e24",
    "name": "company",
    "scope": "user",
    "secret": true,
    "uid": "key_value_pair:user:company",
    "value": "0083E1033A54F9FAB3336FDA3F6FE0A658A02A21DC6BA530A5FB062B13999A85418906DEE8D62CFD13BDF64863013DBEDAB998C742D4767A10"
}

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$ http "http://localhost:9101/v2/keys/user/company?decrypt=true"
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Content-Type,Authorization,X-Auth-Token,St2-Api-Key,X-Request-ID
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Access-Control-Allow-Origin: http://172.168.50.50:3000
Access-Control-Expose-Headers: Content-Type,X-Limit,X-Total-Count,X-Request-ID
Connection: keep-alive
Content-Length: 194
Content-Type: application/json; charset=UTF-8
Date: Sat, 07 May 2016 01:10:53 GMT
X-Request-Id: 623d82d8-bc63-45e1-a4a7-4c0743e93c72

{
    "encrypted": false,
    "id": "572d4086d9d7ed14d88a3e24",
    "name": "company",
    "scope": "user",
    "secret": true,
    "uid": "key_value_pair:user:company",
    "value": "BROcade"
}

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$

Kami · 2016-05-05T04:05:32Z

st2common/st2common/models/api/keyvalue.py

            doc['value'] = symmetric_decrypt(KeyValuePairAPI.crypto_key, model.value)
            encrypted = False

+        scope = getattr(model, 'scope', SYSTEM_KV_PREFIX)


I personally view scope and key prefix as two different things and they don't need to be the same (scope is a user visible feature and key prefix for a particular scope is an implementation detail).

In any case, I would have those scopes:

user - User scopes, keys are prefixed with some common prefix for this scope (user..fooor_user..foo`)

global - Anything which doesn't have a prefix (so any other existing key). We could explicitly prefix keys with a global scope, but the question is how to handle the keys without the prefix then.

Or do you want to introduce also a concept of no scope?

I like "user" and "global" scopes as well. I even anticipate more scopes like "environment" etc. Our current story for key value store is everything is global and you can "refer" to a variable via {{system.foo}} even though "foo" is the actual key name. So for backward compatibility, I am setting the scope to "system" and don't want to introduce another name "global". If you guys think this is a bad idea, we should talk. /cc: @manasdk

If we did design this from scratch we would have the scope property and assign it to system/global by default. The other choice would be to have {{system.foo}} and {{system.user.foo}} where system is still a prefix and what follows is possibly a scope i.e. user or something else in the future if we allow for user configurable scopes. I actually do prefer system transitioning to a scope although it is really from the scope perspective better named global. I wish I had been prescient and made space for this when I added ability to look up kv-store values in rules, actions etc.

Taking this forward it would mean that when {{system.foo}} and {{user.foo}} we now grab 2 top level words i.e. system and user for the context addressable space. Not ideal but not really much worse that what we have already. I feel we should only grab {{$user.foo}} or some such obscure token where 2 purposes are served -

$ suggest it will be replaced

$user is less-likely to appear in an addressable context

manasdk · 2016-05-05T21:49:53Z

st2api/st2api/controllers/v1/keyvalue.py

+                from_model_kwargs=from_model_kwargs,
+                **kwargs
+            )
+            kvp_db = kvp_db[0] if kvp_db else None


why/how would get_one by name+scope return multiple values?

I feel this code needs to be in the service layer where there is a method get_one(scope, name)

why/how would get_one by name+scope return multiple values?

It is not returning more than one value. It simply returns an array with one item which is both counter intuitive and blows up CLI.

manasdk · 2016-05-05T22:19:39Z

st2common/st2common/models/db/keyvalue.py


    name = me.StringField(required=True, unique=True)
    value = me.StringField()
    secret = me.BooleanField(default=False)
    expire_timestamp = me.DateTimeField()
+    scope = me.StringField(default=SYSTEM_KV_PREFIX)


What happens to old data in DB with new code? Still works?

I captured it in a TODO item. Backward compatibility. Yet to be done.

This is what happens when I read code and dont read the description :P

manasdk · 2016-05-05T22:24:29Z

@lakshmi-kannan What does st2 key list show? Would there be a scope column?

lakshmi-kannan · 2016-05-05T22:28:05Z

@manasdk Not yet

(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●●)$ st2 key list                    [ruby-1.9.3p484]
+------+-------+--------+-----------+------------------+
| name | value | secret | encrypted | expire_timestamp |
+------+-------+--------+-----------+------------------+
| foo  | bar   | False  | False     |                  |
+------+-------+--------+-----------+------------------+
(virtualenv)vagrant@st2dev /mnt/src/storm/st2 (issue_167/user_scoped_vars●)$

lakshmi-kannan · 2016-05-07T01:04:30Z

st2api/st2api/controllers/resource.py

@@ -242,6 +242,25 @@ def _get_from_model_kwargs_for_request(self, request):
        """
        return self.from_model_kwargs

+    def _get_one_by_scope_and_name(self, scope, name, from_model_kwargs=None):


@manasdk FYI

* master: (62 commits) Update affected tests. Update affected test. Remove some unecessary duplicated variable declarations. Update a base RBAC tests class to insert a user with no permissions and role assignments. Add RBAC tests for runner types API endpoint. Update "_get_by_name_or_id" method so it's consistent with "_get_by_ref_or_id" and throws if a resource is not found. Update changelog. Remove now old and unused assertion methods. Update more RBAC related assertion methods and update existing tests to use those new methods. Add more developer-friendly assertion methods and update affected code to utilize those new methods. Fix lint. Add new assertion methods for asserting RBAC permissions grants and update affected tests to use those new methods. Add new _user_doesnt_have_resource_db_permissions assertion method which is the inverse of the existing one and update tests to use it. Add a test case for disabled runner. Update more affected tests. Update affected tests - add missing required "name" attribute to the RunnerTypeDB objects. Use getattr, weak typing ftl. Add RBAC resolver tests for runner type resolver. Add a test case for disabling and re-enabling a runner. Only allow "enabled" attribute of the runner to be updated via the API. ...

* master: Add a test case for it. Update changelog. Allow register-setup-virtualenvs flag to be used in combination with register-all in the `st2-register-content script. Add missing abspath call. Update changelog.# On branch pack_test_fixture_loading_utils Add new "get_fixture_content" method to all the pack resource test classes. Conflicts: CHANGELOG.rst

Kami · 2016-05-16T13:30:48Z

st2api/st2api/controllers/resource.py

+        """
+        instance = self.access.get_by_scope_and_name(scope=scope, name=name)
+        if not instance:
+            return instance


_get_one_* methods usually return 404 (pecan.abort) if a object is not found (and _get_by_* throw StackStormDBObjectNotFoundError if an object is not found, and _get_one methods usually call _get_by methods).

We should do the same here for consistency and also add corresponding test case.

Also seems like this is kinda key value pair controller specific so maybe it should live in base key value pair controller or similar?

You made that change (StackStormDBObjectNotFoundError) already. I'll wait for you to merge that and make the corresponding change here.

Also seems like this is kinda key value pair controller specific so maybe it should live in base key value pair controller or similar?

I had it in KeyValuePairController and manas said move it to some base layer. Geez. Ignoring.

Addressed StackStormDBObjectNotFoundError - feef877

Lesson -> don't listen to manas :P

j/k

Kami · 2016-05-16T13:59:10Z

I've added some in-line comments.

Overall, I'm fine with other changes, but as mentioned on Slack, I would remove v2 stuff from this PR.

I think we all need to get on the same page and have a consistent story for the v2 API so we don't need to deprecate v2 yet again in the near future when we plan to work on an improved API.

Also, what's our plan for RBAC here? Will this be done separately, or?

manasdk · 2016-05-16T15:28:11Z

I would remove v2 stuff from this PR.

What is wrong with it? is the v2 API bad already?

Kami · 2016-05-16T15:31:10Z

@manasdk The problem is that it's a one off-thing.

We need a consistent story and plan for it (that means how paths are going to look like, responses, etc.). I'm fine with adding it as soon as we have a consistent story and plan for it, because then we can make sure this new v2 API follows all of those conventions.

Tomorrow I plan to start a discussion thread on v2 API and we can continue discussion about that there.

manasdk · 2016-05-16T15:37:08Z

The problem is that it's a one off-thing.

Is it ad-hoc? Isn't this exactly the reason i.e. we are changing a model therefore need to have a new endpoint. I am fine with the discussion driving the impl and then coming around to picking up changes here but why would you suggest reverting the changes?

Kami · 2016-05-16T15:52:22Z

@manasdk Yes, and the same end result can be achieved using v1 API so I see no point in rushing v2 API until we have a clear picture on how we want it to look.

* master: (28 commits) register ACTIONEXECUTIONSTATE_XCHG register LIVEACTION_STATUS_MGMT_XCHG exchange by default For consistency, make sure that _get_by method doesn't throw. Fix assertion method name. Add tests for config schema API endpoints. Fix lint. Update packs.uninstall action to also delete corresponding ConfigSchemaDB object. Now that it's a top-level endpoint it makes sense to have "get all" / list endpoint. Don't use pack cache in the tests. Add tests for pack and config schema registrar. Update changelog. Add config schema fixture for dummy_pack_1. Fix lint, add missing file. Add API endpoints RBAC tests for pack config schema. Fix RBAC for Pack Config Schema. Add "get_by_pack" method and fix resource registrar. Add comment and assertion to detect programmer errors. Fix "_get_by_pack_ref" method to throw if the resource doesn't exist. Update affected test - this user is now added as part of the base class. Fix dummy pack metadata. ... Conflicts: CHANGELOG.rst

lakshmi-kannan · 2016-05-18T03:25:20Z

@manasdk @Kami : Removed v2 APIs here 67d7ed9

lakshmi-kannan · 2016-05-18T03:26:21Z

@Kami: > Also, what's our plan for RBAC here? Will this be done separately, or?

You should read the description sometimes before complaining everywhere :P

Kami · 2016-05-18T10:45:23Z

st2api/st2api/controllers/root.py

@@ -33,9 +34,12 @@ class RootController(BaseRootController):

    def __init__(self):
        v1_controller = v1_root.RootController()
+        v2_controller = v2_root.RootController()


Probably forgot to remove this?

Lakshmi Kannan added 2 commits May 4, 2016 14:21

Introduce 'scope' field in key value model

849ae4f

Reject invalid scopes

631ebc7

Kami reviewed May 5, 2016
View reviewed changes

Support GET one for keys with scope

a1ab9d3

manasdk reviewed May 5, 2016
View reviewed changes

Support LIST operation on scoped variables

40df77f

manasdk reviewed May 5, 2016
View reviewed changes

Lakshmi Kannan added 8 commits May 5, 2016 16:42

Migration tool for datastore items

23af69f

Validate scopes on GET and LIST calls for datastore items

8de9c81

Remove duplicate constants from system file

b9b7e8b

Initial commit for v2 controller

d4e9451

Refactor v1 KVP controller

7cf119e

Add a v2 KVP controller

2c5b2b1

Fix delete to work; introduce get by scope and name

8b87901

Mirror fixes in v2 kvp controller

c764125

lakshmi-kannan reviewed May 7, 2016
View reviewed changes

Lakshmi Kannan added 6 commits May 7, 2016 11:25

Fix log formatting error

07a1f91

KVP locks should use scope and name

99af19c

Fix KeyValueLookup for user scoped variables

5bc714f

Add tests for scoped keyvalue lookups

594d3d1

KVP APIs to prefix user keys with actual user name

5a76628

Remove changes to jinja {{user.}} referral

00b39cd

lakshmi-kannan mentioned this pull request May 11, 2016

Passing user context around to rules, sensors and actions #2678

Open

Lakshmi Kannan added 3 commits May 11, 2016 17:36

UserKeyValueLookup class to facilitate user scoped vars lookup

851c80a

Hide user from GET API response for KVP

8c2774a

Add tests for KVP v1 controller to test scoped IO

43595c1

Lakshmi Kannan added 4 commits May 12, 2016 17:20

Fix a typo in docstring

16ed353

Add entry in CHANGELOG

77b7a07

Lint me baby one more time

4078dca

lakshmi-kannan changed the title ~~WIP: Introduce 'scope' field in key value model~~ Introduce 'scope' field in key value model May 13, 2016

Kami reviewed May 16, 2016
View reviewed changes

Lakshmi Kannan added 6 commits May 17, 2016 19:59

Validate scope in v1 controller

5c64e10

Use constant for system scope

e113f08

Use UserKeyReference

81b76ef

Remove v2 APIs

67d7ed9

Raise StackStormDBObjectNotFoundError for consistency

feef877

lakshmi-kannan merged commit 483b2a6 into master May 18, 2016

lakshmi-kannan deleted the issue_167/user_scoped_vars branch May 18, 2016 03:39

Kami reviewed May 18, 2016
View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Introduce 'scope' field in key value model #2669

Introduce 'scope' field in key value model #2669

lakshmi-kannan commented May 4, 2016 •

edited

Loading

Kami May 5, 2016

lakshmi-kannan May 5, 2016

manasdk May 5, 2016

manasdk May 5, 2016

lakshmi-kannan May 5, 2016

manasdk May 5, 2016

lakshmi-kannan May 5, 2016

manasdk May 5, 2016

manasdk commented May 5, 2016

lakshmi-kannan commented May 5, 2016

lakshmi-kannan May 7, 2016

Kami May 16, 2016

Kami May 16, 2016

lakshmi-kannan May 18, 2016 •

edited

Loading

lakshmi-kannan May 18, 2016

lakshmi-kannan May 18, 2016

Kami May 18, 2016

Kami commented May 16, 2016

manasdk commented May 16, 2016

Kami commented May 16, 2016

manasdk commented May 16, 2016

Kami commented May 16, 2016

lakshmi-kannan commented May 18, 2016

lakshmi-kannan commented May 18, 2016 •

edited

Loading

Kami May 18, 2016

Introduce 'scope' field in key value model #2669

Introduce 'scope' field in key value model #2669

Conversation

lakshmi-kannan commented May 4, 2016 • edited Loading

TODO:

CLI examples:

GET

LIST

v2 API examples

PUT

DELETE

GET

v2 APIs with secrets

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

manasdk commented May 5, 2016

lakshmi-kannan commented May 5, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lakshmi-kannan May 18, 2016 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Kami commented May 16, 2016

manasdk commented May 16, 2016

Kami commented May 16, 2016

manasdk commented May 16, 2016

Kami commented May 16, 2016

lakshmi-kannan commented May 18, 2016

lakshmi-kannan commented May 18, 2016 • edited Loading

Choose a reason for hiding this comment

lakshmi-kannan commented May 4, 2016 •

edited

Loading

lakshmi-kannan May 18, 2016 •

edited

Loading

lakshmi-kannan commented May 18, 2016 •

edited

Loading