Simon
My feedback
20 results found
-
2 votesSimon shared this idea ·
-
36 votesSimon supported this idea ·
-
16 votesSimon supported this idea ·
An error occurred while saving the comment -
20 votesSimon supported this idea ·
-
2 votesSimon supported this idea ·
-
70 votesSimon supported this idea ·
-
3 votesSimon supported this idea ·
-
160 votesSimon supported this idea ·
-
20 votesSimon supported this idea ·
-
13 votesSimon shared this idea ·
-
2 votesSimon supported this idea ·
-
3 votesSimon supported this idea ·
-
9 votesSimon supported this idea ·
-
19 votesSimon supported this idea ·
-
32 votesSimon supported this idea ·
-
32 votesSimon supported this idea ·
-
100 votesSimon supported this idea ·
-
189 votesSimon supported this idea ·
-
101 votesSimon supported this idea ·
-
418 votes
An error occurred while saving the comment Simon commentedEnabling granular permission at the API level would also be helpful. For example I want to set up a process to pull Metrics into Prometheus, I would like to be able to set up an API key that just has the ability to perform this task on just this particular API resource.
Simon supported this idea ·
Agree it would be nice to have this natively within Atlas. Until that day though we're looking to implement this using scheduled triggers.