You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The S3 bucket stuff is for storing Terraform state; technically SSE-C is optional, but it's a good security practice. You can use AWS S3 for it, doesn't have to be Backblaze B2 like we use.
Repository secrets
CORELLIUM_API_TOKEN
e.g. 123.123
This should be an API token from an admin on an enterprise account.
CORELLIUM_API_TOKEN_PERSONAL
e.g. 123.123
This should be an API token from a user on a personal cloud account.
S3_SECRET_KEY
e.g. K000Aa00+aAAAA0AA+AAaa0AAaaaaAA
AWS_SSE_CUSTOMER_KEY
e.g. 6FdlsdjNZpAjJTeT9dDQ5KTugdp4YFchc8va7LcwzHg=
You can generate this random key with:
openssl rand -base64 32
Repository variables
CORELLIUM_API_HOST
e.g. terraform.enterprise.corellium.com
S3_ACCESS_KEY
e.g. 1234567890123456789012345
S3_BUCKET
e.g. terraform-provider-corellium-github-action-state-bucket
S3_ENDPOINT
e.g. https://s3.us-east-005.backblazeb2.com
S3_REGION
e.g. us-east-005
The text was updated successfully, but these errors were encountered:
The S3 bucket stuff is for storing Terraform state; technically SSE-C is optional, but it's a good security practice. You can use AWS S3 for it, doesn't have to be Backblaze B2 like we use.
Repository secrets
CORELLIUM_API_TOKEN
e.g.
123.123
This should be an API token from an admin on an enterprise account.
CORELLIUM_API_TOKEN_PERSONAL
e.g.
123.123
This should be an API token from a user on a personal cloud account.
S3_SECRET_KEY
e.g.
K000Aa00+aAAAA0AA+AAaa0AAaaaaAA
AWS_SSE_CUSTOMER_KEY
e.g.
6FdlsdjNZpAjJTeT9dDQ5KTugdp4YFchc8va7LcwzHg=
You can generate this random key with:
Repository variables
CORELLIUM_API_HOST
e.g.
terraform.enterprise.corellium.com
S3_ACCESS_KEY
e.g.
1234567890123456789012345
S3_BUCKET
e.g.
terraform-provider-corellium-github-action-state-bucket
S3_ENDPOINT
e.g.
https://s3.us-east-005.backblazeb2.com
S3_REGION
e.g.
us-east-005
The text was updated successfully, but these errors were encountered: