You're right, I didn't really think through the specific configs that each
sensor has across enrichment and indexing (because even indexing has the
various batch tuning configurations). I was thinking in terms of topology,
which isn't complete. Really it should (probably) be in terms of sensor all
> @Mike Yeah, I agree. The Jira for that doesn't exist yet, pretty much
pending this exact conversation winding down.
Yup, understood.
On Fri, Nov 30, 2018 at 7:36 AM Justin Leet wrote:
> To start with, I'm thinking just the configuration, in particular anything
> that touches the
Would it be based on the operation as well? Like be able to read or modify.
So is this scenario valid? from the user experience perspective, a user may
be authorised to change the indexing/enrichment config (because there is
only one topology for them), but because he/she doesn't have sufficient
To start with, I'm thinking just the configuration, in particular anything
that touches the ConfigurationsUtils. I think for the first pass, we could
leave reading from configs out of it and focus on who can write configs
(since that's more disruptive to the system).
To the best of my knowledge,
Justin, It probably makes sense to provide a list of these configuration
items as subtasks on the FB Jira so that we can crosscheck what entry
points have been implemented against the test scripts. Do you think this
will impact streaming enrichments or the profiler at all? That is to say,
as Ali
Hi Justin,
By configuration do you mean the sensor related configurations only? Are
you limiting the scope of this activity to the management-UI or also
Alert-UI as well? For example, defining different roles (pre-defined
or customizable) and the fine-grained integration with Ranger?
Cheers,
Ali
Hi Justin,
By configuration do you mean the sensor related configurations only? Are
you limiting the scope of this activity to the management-UI or also
Alert-UI as well? For example, defining different roles (pre-defined
or customizable) and the fine-grained integration with Ranger?
Cheers,
Ali
Hi all,
Sorry for the second copy of this email, I forgot the [DISCUSS] tag on the
original. Otherwise, this has the same content.
Right now, our various configs can be modified by anyone with access to the
various scripts. I'd like to start a discussion around building out some
authorization
Hi all,
Right now, our various configs can be modified by anyone with access to the
various scripts. I'd like to start a discussion around building out some
authorization to be able to add some more fine grained controls around this.
Other projects have some variants on how to accomplish this.
