feat(4.22.0): bumped to aws provider 4.22.0 and added grafana, amp

[haarchri]

Signed-off-by: haarchri chhaar30@googlemail.com

Description of your changes

• bumped from 3.52.0 to 4.22.0 terraform aws-provider
• added grafana
• added amp
• changed route53 include list, trafficpolicy* was added - have no use-case to test - so skipped for now 2 resources

breaking changed because of provider bump:

• elasticache.aws.jet.crossplane.io_replicationgroups.yaml autoMinorVersionUpgrade changed type: boolean to type: string

• elbv2.aws.jet.crossplane.io_lbtargetgroups.yaml deregistrationDelay: changed type: number to type: string

• s3.aws.jet.crossplane.io_buckets.yaml Changed field websiteDomain and websiteEndpoint to additionalProperties

  Grafana and AMP (Prometheus)

  NAME                                                       READY   SYNCED   EXTERNAL-NAME   AGE
  workspace.grafana.aws.jet.crossplane.io/sample-workspace   True    True     g-aa57ea1300    52m
  
  NAME                                                             READY   SYNCED   EXTERNAL-NAME        AGE
  roleassociation.grafana.aws.jet.crossplane.io/sample-workspace   True    True     g-aa57ea1300/ADMIN   29m
  
  NAME                                                   READY   SYNCED   EXTERNAL-NAME                             AGE
  workspace.amp.aws.jet.crossplane.io/sample-workspace   True    True     ws-a9f6db36-8752-419a-ba71-5021769790f7   14m

[haarchri]

@muvaf @jbw976 regarding api group version for new resources like grafana, amp/prometheus ? did we use v1alpha1 or v1alpha2 ?

[haarchri]

currently checking why observed is failing locally with make run for existing resources with:

.657479674736587e+09 DEBUG events Warning {"object": {"kind":"LBTargetGroup","name":"sample-lambda-targetgroup","uid":"34dee55d-e325-4b74-ae36-62ba5a45d01f","apiVersion":"elbv2.aws.jet.crossplane.io/v1alpha2","resourceVersion":"282025"}, "reason": "CannotObserveExternalResource", "message": "cannot run refresh: refresh failed: Provider requirements cannot be satisfied by locked dependencies: The following required providers are not installed:\n\n- registry.terraform.io/hashicorp/aws (4.22.0)\n\nPlease run \"terraform init\"."}

[jbw976]

@haarchri I believe new resources, that are configured with external name, late init, cross resource references, etc. have been introduced at v1alpha2 in the past :)

[ytsarev]

@haarchri maybe it is a local invocation artifact. What will happen if you clean up the temporary terraform workspace directory?

[haarchri]

It's the same - i cleaned up because otherwise the make generate is not working with new version

[ytsarev]

We may be talking about different directories, I mean something like /var/folders/sx/$uuid/T/$another_uuid/ on macos or similar temp dir on linux.

They contain

main.tf.json
terraform.tfstate
terraform.tfstate.backup

of specific MR and definitely should not affect any code generation

[haarchri]

@ytsarev yeah - thanks for the hint

/var/folders/cz/2y38s5w127n7vc997qmxcsnr0000gn/T/a986a902-20ff-433a-b8cb-6b12c97a9208 removed the folder now it looks better