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

about Monitor Authentication #551

Open
go-test-sysdig opened this issue Aug 30, 2024 · 2 comments
Open

about Monitor Authentication #551

go-test-sysdig opened this issue Aug 30, 2024 · 2 comments
Labels
stale This has become stale due to inactivity

Comments

@go-test-sysdig
Copy link

I am going to add a Role using tf, although my mistake caused me to write the wrong option in the authentication, the Role addition still succeeded, is this the correct situation?
Here's the tf file I used, and you can see that I wrote “sysdig_monitor_api_token” instead of “sysdig_secure_api_token”.

terraform {
  required_providers {
    sysdig = {
      source = "sysdiglabs/sysdig"
      version = ">=0.5"
    }
  }
}

provider "sysdig" {
  sysdig_secure_url="https://secure.sysdig.com"
  sysdig_monitor_api_token  = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

I just tried adding Role and Team.
Adding a Role worked but adding a Team failed.

@dbonf
Copy link
Collaborator

dbonf commented Sep 3, 2024

hi, not sure if I understood what resources you tried to create, I assume a sysdig_custom_role and a sysdig_secure_team?

In that case, the fact that the custom role was created and the team was not is expected, since sysdig_custom_role is a resource that can be created by defining either secure product credentials or monitor product credentials (it is listed under "Sysdig Platform" in the doc), while the sysdig_secure_team is a resource that can be created only with secure product credentials (it is listed under "Sysdig Secure"), and if you need a monitor team, you create the sysdig_monitor_team companion resource.

Copy link

github-actions bot commented Nov 3, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale This has become stale due to inactivity label Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale This has become stale due to inactivity
Projects
None yet
Development

No branches or pull requests

2 participants