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.

Sign up for GitHub

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

Jump to bottom

Lacework Agents access token resource and data source #41

Closed
JPLachance opened this issue Nov 10, 2020 · 2 comments · Fixed by #45
Closed

Lacework Agents access token resource and data source #41

JPLachance opened this issue Nov 10, 2020 · 2 comments · Fixed by #45
Assignees
@afiune
Labels
feat New feature or request

Comments

@JPLachance
Copy link

Greetings,

Today, to manage Lacework agents access tokens, we must use the Lacework UI or the API.

With a Terraform resource, automating the creation and management of Lacework agents access tokens will be easier. For example, it will make it easy to create the access token and then store it in AWS Secrets Manager.

Thanks in advance for the help!
@afiune afiune added the feat New feature or request label Nov 11, 2020
@afiune afiune self-assigned this Dec 1, 2020
@afiune afiune mentioned this issue Dec 7, 2020
Merged
@afiune
Copy link
Contributor

afiune commented Dec 7, 2020

@JPLachance Would this resource and this data source work for you?

Resource

resource "lacework_agent_access_token" "k8s" {
  name        = "prod"
  description = "k8s deployment for production env"
}

Data Source

data "lacework_agent_access_token" "k8s" {
  name  = "prod"
}

Both expose a token attribute. Suggestions are accepted.

@JPLachance
Copy link
Author

Hello!

This will work. It will allow me to create token, store it in AWS Secrets Manager, automate its rotation.

Thank you 😄

afiune added a commit that referenced this issue Dec 8, 2020
@afiune
feat(resource): new lacework_agent_access_token
564c670 
** lacework_agent_access_token

To connect to the Lacework platform, Lacework agents require an agent access token. Use this resource to
mange agent tokens within your Lacework account.

!> **Warning:** Agent tokens should be treated as secret and not published. A token uniquely identifies
a Lacework customer. If you suspect your token has been publicly exposed or compromised, generate a new
token, update the new token on all machines using the old token. When complete, the old token can safely
be disabled without interrupting Lacework services.

You can use the agent token name to logically separate your deployments, for example, by environment types
(QA, Dev, etc.) or system types (CentOS, RHEL, etc.).

-> **Note:** The Lacework agent runs on most Linux distributions. For more detailed information, see
	[Supported Operating Systems.](https://support.lacework.com/hc/en-us/articles/360005230014-Supported-Operating-Systems).

!> **Warning:** By design, agent tokens cannot be deleted. Running terraform destroy will only disable the token.

** Example Usage

```hcl
resource "lacework_agent_access_token" "k8s" {
  name        = "prod"
  description = "k8s deployment for production env"
}
```

** Argument Reference

The following arguments are supported:

* `name` - (Required) The agent access token name.
* `description` - (Optional) The agent access token description.
* `enabled` - (Optional) The state of the external integration. Defaults to `true`.

** Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

* `token` - The agent access token.

** Import

A Lacework agent access token can be imported using the token itself, e.g.

```
$ terraform import lacework_agent_access_token.k8s YourAgentToken
```
-> **Note:** To list all agent access tokens in your Lacework account, use the
	Lacework CLI command `lacework agent token list`. To install this tool follow
	[this documentation](https://github.com/lacework/go-sdk/wiki/CLI-Documentation#installation).

Closes #41

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
@afiune afiune mentioned this issue Dec 8, 2020
Merged
afiune added a commit that referenced this issue Dec 8, 2020
@afiune
feat(resource): new lacework_agent_access_token
869ba3a 
** lacework_agent_access_token

To connect to the Lacework platform, Lacework agents require an agent access token. Use this resource to
mange agent tokens within your Lacework account.

!> **Warning:** Agent tokens should be treated as secret and not published. A token uniquely identifies
a Lacework customer. If you suspect your token has been publicly exposed or compromised, generate a new
token, update the new token on all machines using the old token. When complete, the old token can safely
be disabled without interrupting Lacework services.

You can use the agent token name to logically separate your deployments, for example, by environment types
(QA, Dev, etc.) or system types (CentOS, RHEL, etc.).

-> **Note:** The Lacework agent runs on most Linux distributions. For more detailed information, see
	[Supported Operating Systems.](https://support.lacework.com/hc/en-us/articles/360005230014-Supported-Operating-Systems).

!> **Warning:** By design, agent tokens cannot be deleted. Running terraform destroy will only disable the token.

** Example Usage

```hcl
resource "lacework_agent_access_token" "k8s" {
  name        = "prod"
  description = "k8s deployment for production env"
}
```

** Argument Reference

The following arguments are supported:

* `name` - (Required) The agent access token name.
* `description` - (Optional) The agent access token description.
* `enabled` - (Optional) The state of the external integration. Defaults to `true`.

** Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

* `token` - The agent access token.

** Import

A Lacework agent access token can be imported using the token itself, e.g.

```
$ terraform import lacework_agent_access_token.k8s YourAgentToken
```
-> **Note:** To list all agent access tokens in your Lacework account, use the
	Lacework CLI command `lacework agent token list`. To install this tool follow
	[this documentation](https://github.com/lacework/go-sdk/wiki/CLI-Documentation#installation).

Closes #41

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
@afiune afiune closed this as completed in #45 Dec 8, 2020
afiune added a commit that referenced this issue Dec 8, 2020
@afiune
feat(resource): new lacework_agent_access_token (#45)
de8b2cc 
To connect to the Lacework platform, Lacework agents require an agent access token. Use this resource to
manage agent tokens within your Lacework account.

!> **Warning:** Agent tokens should be treated as secret and not published. A token uniquely identifies
a Lacework customer. If you suspect your token has been publicly exposed or compromised, generate a new
token, update the new token on all machines using the old token. When complete, the old token can safely
be disabled without interrupting Lacework services.

You can use the agent token name to logically separate your deployments, for example, by environment types
(QA, Dev, etc.) or system types (CentOS, RHEL, etc.).

-> **Note:** The Lacework agent runs on most Linux distributions. For more detailed information, see
	[Supported Operating Systems.](https://support.lacework.com/hc/en-us/articles/360005230014-Supported-Operating-Systems).

!> **Warning:** By design, agent tokens cannot be deleted. Running terraform destroy will only disable the token.

** Example Usage

```hcl
resource "lacework_agent_access_token" "k8s" {
  name        = "prod"
  description = "k8s deployment for production env"
}
```

** Argument Reference

The following arguments are supported:

* `name` - (Required) The agent access token name.
* `description` - (Optional) The agent access token description.
* `enabled` - (Optional) The state of the external integration. Defaults to `true`.

** Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

* `token` - The agent access token.

** Import

A Lacework agent access token can be imported using the token itself, e.g.

```
$ terraform import lacework_agent_access_token.k8s YourAgentToken
```
-> **Note:** To list all agent access tokens in your Lacework account, use the
	Lacework CLI command `lacework agent token list`. To install this tool follow
	[this documentation](https://github.com/lacework/go-sdk/wiki/CLI-Documentation#installation).

Closes #41

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
afiune added a commit that referenced this issue Dec 8, 2020
@afiune
feat(data-source): new lacework_agent_access_token
6283e63 
To have parity with our resource `lacework_agent_access_token` we are
adding a new data source to retrieve Agent access tokens by looking up
for the Token Alias. (a.k.a Token Name)

Contributes #41

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
@afiune afiune mentioned this issue Dec 8, 2020
Merged
dmurray-lacework pushed a commit that referenced this issue May 27, 2021
@afiune @dmurray-lacework
feat(resource): new lacework_agent_access_token (#45)
ebd2540 
To connect to the Lacework platform, Lacework agents require an agent access token. Use this resource to
manage agent tokens within your Lacework account.

!> **Warning:** Agent tokens should be treated as secret and not published. A token uniquely identifies
a Lacework customer. If you suspect your token has been publicly exposed or compromised, generate a new
token, update the new token on all machines using the old token. When complete, the old token can safely
be disabled without interrupting Lacework services.

You can use the agent token name to logically separate your deployments, for example, by environment types
(QA, Dev, etc.) or system types (CentOS, RHEL, etc.).

-> **Note:** The Lacework agent runs on most Linux distributions. For more detailed information, see
	[Supported Operating Systems.](https://support.lacework.com/hc/en-us/articles/360005230014-Supported-Operating-Systems).

!> **Warning:** By design, agent tokens cannot be deleted. Running terraform destroy will only disable the token.

** Example Usage

```hcl
resource "lacework_agent_access_token" "k8s" {
  name        = "prod"
  description = "k8s deployment for production env"
}
```

** Argument Reference

The following arguments are supported:

* `name` - (Required) The agent access token name.
* `description` - (Optional) The agent access token description.
* `enabled` - (Optional) The state of the external integration. Defaults to `true`.

** Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

* `token` - The agent access token.

** Import

A Lacework agent access token can be imported using the token itself, e.g.

```
$ terraform import lacework_agent_access_token.k8s YourAgentToken
```
-> **Note:** To list all agent access tokens in your Lacework account, use the
	Lacework CLI command `lacework agent token list`. To install this tool follow
	[this documentation](https://github.com/lacework/go-sdk/wiki/CLI-Documentation#installation).

Closes #41

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
dmurray-lacework pushed a commit that referenced this issue May 27, 2021
@afiune @dmurray-lacework
feat(data-source): new lacework_agent_access_token
7ac5f2e 
To have parity with our resource `lacework_agent_access_token` we are
adding a new data source to retrieve Agent access tokens by looking up
for the Token Alias. (a.k.a Token Name)

Contributes #41

Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afiune afiune

Labels
feat New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(resource): new lacework_agent_access_token lacework/terraform-provider-lacework
2 participants
@JPLachance @afiune