lizzha
commented
7 years ago The error was generated when creating cfclient. Could you please share the manifest settings, and the CF version that you used?
Open siennathesane opened 7 years ago
lizzha
commented
7 years ago The error was generated when creating cfclient. Could you please share the manifest settings, and the CF version that you used?
siennathesane
commented
7 years ago PCF 1.11 was the target platform.
Mike. On Wed, Aug 23, 2017 at 7:44 PM Liz Zhang notifications@github.com wrote:
The error was generated when creating cfclient. Could you please share the manifest settings, and the CF version that you used?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/oms-log-analytics-firehose-nozzle/issues/1#issuecomment-324508891, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMEsbpW8kINjF03gRof-fTAZSgw3W6sks5sbNVvgaJpZM4PAWoo .
-- Thanks!
Mike Lloyd USMC 808-633-8998
lizzha
commented
7 years ago It was tested working against PCF 1.11. It would help if you could share the manifest settings, and make sure the FIREHOSE_USER has access cloud_controller.admin_read_only (or cloud_controller.admin) and doppler.firehose.
siennathesane
commented
7 years ago Here is my Firehose user, oms. It has cloud_controller.admin and doppler.firehose privileges. I followed the README steps for creating this user.
-
id: ee126321-b759-4e0b-9cbf-3572defb19e4
meta
version: 0
created: 2017-08-23T00:45:10.000Z
lastmodified: 2017-08-23T00:45:10.000Z
name
familyname: oms
givenname: oms
emails:
-
value: oms
primary: false
groups:
-
value: 753fe23a-31da-442b-8700-616077046a1d
display: uaa.offline_token
type: DIRECT
-
value: 71283fac-8a25-4dae-82d4-ad7437093388
display: profile
type: DIRECT
-
value: 6fe002f4-16be-4444-9bb5-ca6fd103d704
display: cloud_controller.read
type: DIRECT
-
value: 6c050cb5-38ac-45fe-b214-ae9738fa8da7
display: cloud_controller.admin
type: DIRECT
-
value: e9301770-5100-4661-a536-e92fd4b22040
display: openid
type: DIRECT
-
value: 096e3d26-1a45-4056-aff4-d97556d1a289
display: user_attributes
type: DIRECT
-
value: 2d3eb75d-9ba9-45fc-a47b-a987a6c20655
display: oauth.approvals
type: DIRECT
-
value: b1b46c49-5c34-42db-9d44-6af28fa8e6d2
display: cloud_controller.write
type: DIRECT
-
value: fa417f84-4f28-43e1-8d2e-f9172ec75e4a
display: notification_preferences.write
type: DIRECT
-
value: 9f821307-77e3-4d84-be14-c122f134e2d6
display: uaa.user
type: DIRECT
-
value: e0f1ab6d-e202-4e86-80bd-6333e40c97b2
display: notification_preferences.read
type: DIRECT
-
value: de17236b-2f0a-4566-b53b-803c9c084ab0
display: cloud_controller_service_permissions.read
type: DIRECT
-
value: 33e94367-9bae-4a20-b180-732216b28a92
display: actuator.read
type: DIRECT
-
value: 05a1176e-9332-4d45-9ca4-df5fbcfd6003
display: cloud_controller.user
type: DIRECT
-
value: ce6c4fb8-d2e0-4db2-8f10-13fb336869af
display: doppler.firehose
type: DIRECT
-
value: 8796f9bb-3903-4c6a-a1cd-f2063ba4d14d
display: password.write
type: DIRECT
-
value: 6882bb03-baea-47bd-8c76-22bdc4b25a0b
display: scim.me
type: DIRECT
-
value: c2782e94-1cbf-447c-9c13-9f716575718d
display: approvals.me
type: DIRECT
-
value: e578e8c4-efd0-46f6-8dc6-43b444522274
display: roles
type: DIRECT
approvals:
active: true
verified: true
origin: uaa
schemas: urn:scim:schemas:core:1.0
username: oms
zoneid: uaa
passwordlastmodified: 2017-08-23T00:45:10.000ZThanks. I'm not able to repro this issue. It's possibly related with the API_ADDR (should start with "https://") and FIREHOSE_USER settings.
What do you get by running command:
curl -u
Here's my output:
{
"doppler_logging_endpoint": "wss://doppler.
siennathesane
commented
7 years ago Unfortunately we've already destroyed our Foundation, so I can't do that anymore. Sorry!
On Fri, 25 Aug 2017 at 01:16 Liz Zhang notifications@github.com wrote:
Thanks. I'm not able to repro this issue. It's possibly related with the API_ADDR (should start with "https://") and FIREHOSE_USER settings.
What do you get by running command: curl -u
-k /v2/info ? Here's my output: { "doppler_logging_endpoint": "wss://doppler.
:443", "routing_endpoint": "https://api. /routing", "app_ssh_oauth_client": "ssh-proxy", "app_ssh_host_key_fingerprint": " ", "app_ssh_endpoint": "ssh. :2222", "api_version": "2.82.0", "min_recommended_cli_version": "6.23.0", "name": "", "build": "", "support": "https://support.pivotal.io", "version": 0, "description": "", "authorization_endpoint": "https://login. ", "token_endpoint": "https://uaa. ", "min_cli_version": "6.23.0" } — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Azure/oms-log-analytics-firehose-nozzle/issues/1#issuecomment-324842807, or mute the thread https://github.com/notifications/unsubscribe-auth/AHMEsbpYI3GCQDG23cKqpNSi8Jbjp78qks5sbnTcgaJpZM4PAWoo .
-- Thanks!
Mike Lloyd USMC 808-633-8998
There is an error with the nozzle when trying to unmarshal Doppler data.
I used the latest commit from
master.