tag anoncreds bucket with -dev in dev environment

[aagbsn]

resolve conflict with anoncred_manifests bucket between prod and dev

[github-actions]

Terraform Run Output 🤖

Format and Style 🖌failure

Initialization ⚙️success

Validation 🤖success

Validation Output

$ terraform validate

Warning: Argument is deprecated

  with aws_s3_bucket.anoncred_manifests,
  on main.tf line 246, in resource "aws_s3_bucket" "anoncred_manifests":
 246: resource "aws_s3_bucket" "anoncred_manifests" {

Use the aws_s3_bucket_versioning resource instead

Warning: Available Write-only Attribute Alternative

  with module.ooni_monitoring.aws_ssm_parameter.ooni_monitoring_access_key,
  on ../../modules/ooni_monitoring/main.tf line 47, in resource "aws_ssm_parameter" "ooni_monitoring_access_key":
  47:   value = aws_iam_access_key.ooni_monitoring.id

The attribute value has a write-only alternative value_wo available. Use the
write-only alternative of the attribute when possible.

(and one more similar warning elsewhere)
Success! The configuration is valid, but there were some validation warnings
as shown above.

Plan 📖success

• undefined

Show Plan

$ terraform plan
Acquiring state lock. This may take a few moments...

Pusher	@aagbsn
Action	pull_request
Environment	dev
Workflow	.github/workflows/check_terraform.yml
Last updated	Tue, 27 Jan 2026 16:42:38 GMT

[DecFox]

LGTM! We should just keep in mind to transfer the dev manifest for anon-creds to the new bucket we have after the deployment