AWS introduced longer resource ID format which is mandatory beginning July 2018
(EC2 instances already have that long ID mandatory since December).
The new resource ID format is the resource identifier followed by 17 instead of 8 characters, e.g. for a security group old sg-23hd918d vs new sg-08b8976d0fb53fd18.
In case one of the longer resource IDs is used, boxfuse is currently throwing an error:
com.boxfuse.base.exception.BoxfuseException: Invalid AWS Security Group id: sg-08b8976d0fb53fd18 => ensure it matches ^sg\-[a-f0-9]{8}$
at com.boxfuse.base.types.RegexRestrictedString.<init>(SourceFile:1019)
at com.boxfuse.base.aws.AwsSecurityGroupId.<init>(SourceFile:18)
at com.boxfuse.base.aws.AwsSecurityGroupId.of(SourceFile:14)
at com.boxfuse.generator.config.BoxfuseConfig.configure(SourceFile:278)
at com.boxfuse.client.commandline.Main.main(Main.java:89)
Judging based on the error message, I hope this is a quick fix by just adjusting the regex.
It would be great to support the longer resource IDs for all resources (see the following screenshot for all resources which will receive longer resource IDs)
AWS introduced longer resource ID format which is mandatory beginning July 2018 (EC2 instances already have that long ID mandatory since December).
The new resource ID format is the resource identifier followed by 17 instead of 8 characters, e.g. for a security group old
sg-23hd918d
vs newsg-08b8976d0fb53fd18
.In case one of the longer resource IDs is used, boxfuse is currently throwing an error:
Judging based on the error message, I hope this is a quick fix by just adjusting the regex. It would be great to support the longer resource IDs for all resources (see the following screenshot for all resources which will receive longer resource IDs)
See the EC2 longer resource ID FAQ for more information.