Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to manage Alert Channels at the Organization level #147

Closed
afiune opened this issue Aug 17, 2021 · 0 comments
Closed

Unable to manage Alert Channels at the Organization level #147

afiune opened this issue Aug 17, 2021 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@afiune
Copy link
Contributor

afiune commented Aug 17, 2021

As a Lacework customer that is enrolled in a Lacework organization,
I want to be able to manage my Alert Channels at the Organization level,
So I can manage Alert Channels shared across Lacework sub-accounts.

Bug Description

Today, if any user try to manage an Alert Channel at the Organization level,
for example:

provider "lacework" {
  organization = true
}

resource "lacework_alert_channel_slack" "ops" {
  name = "ops critical alerts"
  slack_url = "https://hooks.slack.com/services/ABCD/12345/abcd1234"
}

The Lacework provider doesn't create (manage) this alert channel at the organization level,
but rather, at the sub-account level.

Proposal Solution

The problem we are facing is the fact that we are migrating the Lacework provider
from API v1 to API v2 and none of the Alert Channels have been migrated to v2.

APIv1 doesn't allow access to organization level data sets, so the solution is to migrate
all Alert channels to APIv2.

JIRA https://lacework.atlassian.net/browse/ALLY-614

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants