tagging all HydroVIS VPP resources

[EdisonOrellana-NOAA]

HydroVIS AWS resources are not tagged in all the environments. Can you work on tagging all HydroVIS VPP resources? Make sure you follow the CCB process. Tagging requirements are documented here [1]. Fernando to share guidance on values for noaa:subcomponent tag.

[1] https://vlab.noaa.gov/redmine/projects/dis-24x7-cloud-support-services/wiki/Tag_Strategy#NWS-Dissemination-Mandatory-Tags

Team - I would suggest the following names for the subcomponent tag.

hydrovis-vpp-fim-dev
hydrovis-vpp-egis
hydrovis-vpp-ops-dash
hydrovis-vpp-other
hydrovis-nwps-web
hydrovis-nwps-api

https://vlab.noaa.gov/redmine/projects/owp-cloud-aws-hydrovis/repository

[RobHanna-NOAA]

For all objects in AWS that have a custom tag called "owp_group" (values of fim-dev or ras2fim")...

1. Either use caution on update all of our objects and keep me posted, so I can review / adjust them. OR
2. Let me fix tags for our objects.

Note: we are only in nws-diss-hydrovis-dev

I am making a twin card for our tagging effort in the inundation-mapping repo issue 1343

[EdisonOrellana-NOAA]

• Changes made to env yamls on vlab repo
• tags added according to tag strategy
• Tags are now a part of IaC and will show up after a redployment
• Pushed to repo for review
• Merged
• Deployment for uat and ti scheduled for Nov 26
• Deployment for prod will happen after ti/uat review or next prod deployment.

[EdisonOrellana-NOAA]

• tag = {} for all aws_s3_objects #1003 Was meant to help solve issues with deployment where s3 objects cannot have more than 10 tags which was causing issues
• Did not work because there is no easy way to override default tags for s3 objects until Terraform AWS Provider V 5.24.0
• In the mean time, I will implement this workaround to create a separate provider for s3 objects. (Thank you Drix!)

• Create separate provider for s3 objects

[RobHanna-NOAA]

Do you think this will cover my Dev/TI 3 s3 buckets? either way, it is fine. We have a script prepared for our S3 buckets ready to go, but if yours covers it, that is fine too. Keep me posted.

@mluck : Something for you to also keep an eye on.

[EdisonOrellana-NOAA]

Hi @RobHanna-NOAA --- Check your s3 buckets, the buckets themselves should be well tagged but the S3 objects themselves inside the buckets should have no tags on them.

If your buckets are part of the IaC then it should cover those.

[EdisonOrellana-NOAA]

• Tagging complete for TI
• IaC code is ready to go for deployment in UAT
• Merge issues are holding up merging in UAT S3 object tags #1005 (looks like question of branching off prod vs ti are in conflict here)
• Plan to discuss branch strategy and best path forward for implementing the tagging code in UAT when Shawn returns

[EdisonOrellana-NOAA]

Update: tagging changes for UAT will be implemented on the next regular deployment ~ week of Jan 6
After that is finished, this issue can be closed.