Update name of subnet fixture, fixing 3 failing integration tests

[clintoncwolfe]

The AWS integration tests were failing on 3 controls, all related to the aws_subnet resource. Here's a sample:

[cwolfe@lodi inspec]$ bundle exec  bin/inspec exec test/integration/aws/default/verify/controls/aws_subnet.rb --attrs test/integration/aws/default/.attribute.yml -t aws://us-east-2/some-profile

Profile: tests from test/integration/aws/default/verify/controls/aws_subnet.rb (tests from test.integration.aws.default.verify.controls.aws_subnet.rb)
Version: (not specified)
Target:  aws://us-east-2

  ×  aws_subnet recall of subnet_01: VPC Subnet  (2 failed)
     ×  VPC Subnet
     aws_subnet Subnet ID must be in the format "subnet-" followed by 8 hexadecimal characters.
     ×  VPC Subnet
     aws_subnet Subnet ID must be in the format "subnet-" followed by 8 hexadecimal characters.
     ✔  VPC Subnet subnet-00000000 should not exist
  ×  aws_subnet properties of subnet_01: VPC Subnet
     ×  VPC Subnet
     aws_subnet Subnet ID must be in the format "subnet-" followed by 8 hexadecimal characters.
  ×  aws_subnet matchers of subnet_01: VPC Subnet
     ×  VPC Subnet
     aws_subnet Subnet ID must be in the format "subnet-" followed by 8 hexadecimal characters.


Profile Summary: 0 successful controls, 3 control failures, 0 controls skipped
Test Summary: 1 successful, 4 failures, 0 skipped

There wasn't anything wrong with the resource; the integration test file was simply looking for the wrong InSpec attribute to figure out the test fixture subnet.

[jquick]

Thanks @clintoncwolfe !

[jerryaldrichiii]

Great catch @clintoncwolfe! Looks good to me.