Skip to content
This repository has been archived by the owner on Jun 20, 2020. It is now read-only.

beat fails without admin or editor groups #13

Closed
josephlewis42 opened this issue Jun 27, 2018 · 2 comments
Closed

beat fails without admin or editor groups #13

josephlewis42 opened this issue Jun 27, 2018 · 2 comments
Labels
bug Something isn't working

Comments

@josephlewis42
Copy link
Contributor

The beat fails with the error Exiting: fail to create subscription: rpc error: code = PermissionDenied desc = User not authorized to perform this action. if it doesn't have the ability to create a subscription on the account, even if the subscription already exists.

As a user I expect to have the ability to configure the beat with a minimal set of permissions--ideally just subscribe--for security purposes and not have it create resources on my account.
@josephlewis42 josephlewis42 added the bug Something isn't working label Jun 27, 2018
@Conky5 Conky5 mentioned this issue Oct 22, 2018
Merged
josephlewis42 pushed a commit that referenced this issue Oct 23, 2018
@josephlewis42
Add setting to avoid subscription creation (#15)
c7dd7d4 
Add a configuration property that will skip attempting to create the
pubsub subscription.

For #13

Note the default subscriber role still will not work, minimal
permissions can be granted as described here
googleapis/google-cloud-node#1502 (comment).
@Conky5
Copy link
Contributor

Conky5 commented Jan 3, 2019

I believe this is closed by #15.

@josephlewis42
Copy link
Contributor Author

I believe you're right!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@josephlewis42 @Conky5