Hello,
I hope we standardize on Hawkular-Tenant at service level. The concept of the persona is
narrow and accounts specific. While we are mapping now personas to tenants that could
change in the future.
Also, the concepts of tenant and multi-tenancy are easier to document and understand by
external consumers. If/when the individual services are decoupled and consumed by other
projects or independently, there is no extra documentation needed to explain the
multi-tenant capability.
Thank you,
Stefan
----- Original Message -----
From: "John Mazzitelli" <mazz(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Thursday, June 11, 2015 9:26:59 AM
Subject: Re: [Hawkular-dev] Tenant no longer in URL in the upcoming Inventory 0.1.0
I thought it was Hawkular-Tenant, not Hawkular-Persona.
I used Hawkular-Tenant header name in my changes to support metrics 0.3.5
The name "Hawkular-Persona" is a new one to me.
----- Original Message -----
> Hi all,
>
> I just wanted to let you know about the breaking change in the upcoming
> Inventory 0.1.0.
>
> Following the suite of metrics, inventory will no longer support the
> tenantID
> in the URL and will solely rely on Hawkular accounts to hand it the
> tenantID
> to use - i.e. it will be the tenant of the currently logged in user or of
> the
> persona passed in using the "Hawkular-Persona" header.
>
> Cheers,
>
> Lukas
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev