Yikes! Sorry about that and thank you for the fix!

However I was wondering if you are modifying that property directly? It's meant to be controlled via a maven profile:
https://github.com/googleapis/java-bigtable/blob/master/google-cloud-bigtable/pom.xml#L260

ie: mvn verify -P bigtable-prod-it

Codecov Report

Merging #91 into master will increase coverage by 0.25%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #91      +/-   ##
============================================
+ Coverage     81.07%   81.33%   +0.25%     
  Complexity      937      937              
============================================
  Files            95       95              
  Lines          5849     5849              
  Branches        311      325      +14     
============================================
+ Hits           4742     4757      +15     
  Misses          916      916              
+ Partials        191      176      -15

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3da95a...55be605. Read the comment docs.

Hope you don't mind, I amended your commit to comply with conventional commit messages

Thanks for the work in checking this in!
We have a need to create the test tables within a VPC Service Controlled security perimeter. This requires us to customize the environment variables.

May I suggest to use a combination?

mvn verify -Pbigtable-prod-it -Dbigtable.project=... -Dbigtable.instance=... -Dbigtable.table=....

The bigtable.env property wasn’t meant to be set directly. Without setting the profile, you will default to the emulator profile which might configure different test cases then the prod profile

Perfect, thank you for the advice. I will modify the invocation accordingly.